Alpha2 Metadata Error on Start
Cantor, Scott
cantor.2 at osu.edu
Wed Jul 30 13:45:11 EDT 2014
On 7/30/14, 1:21 PM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>
>I don't see that I have anything configured that would cause this
>problem, and I'm struggling to follow the cookie trail to where
>FilesystemMetadataResolver is instantiated.
Whatever file is used to load the metadata sources looks like it has a
bean getting defined that has no ID attribute. This is probably a
compatibility bug where we're enforcing a rule we shouldn't be or not
auto-populating an ID that needs to be.
> I'm trying to get our v2
>attribute-resolver.xml and attribute-filter.xml working in v3, so
>maybe there's something in there that needs adjustment. That said, I
>don't see any other errors in the logs to indicate problems with
>resolver or filter configs. Suggestions?
It's a problem with the metadata configuration, not either of those files.
The default services.xml loads metadata from a new file. If you want to
load metadata via relying-party.xml like before, you'd change the
services.xml resources in shibboleth.MetadataResolverResources.
Did you change that? I assume so...
-- Scott
More information about the dev
mailing list