On 11/14/11 10:09 AM, "Brian Abram" <[log in to unmask]> wrote:
>
>-----------------------------------
>Not sure about this but I think the XML is loaded on each run of the
>gss-client
>but if in doubt pkill gss-server and restart it.
I would expect it to only be loaded when mech_eap loads, but I could be
wrong about that.
>Complaints about metadata occurred even though the 'local-login-user'
>came through:
>
>2011-11-14 14:36:01 CRIT Shibboleth.Application : no MetadataProvider
>available, configuration is probably unusable
The configuration can't come with any metadata supplied by default,
there's nothing to give it. If you don't do any attribute filtering based
on metadata, then normal usage of mech_eap is not going to require any
because the security model is RADIUS/AAA, not SAML.
The CRIT behavior is based on standard usage of Shibboleth in which not
having any metadata is akin to a useless installation. I'm considering how
to adjust that, but I don't like that it's calling that a critical error
in the case of Moonshot. If you wouldn't mind filing a bug on it at
https://issues.shibboleth.net, I won't forget to take care of it.
-- Scott
|