A confusing attribute resolver configuration

Brent Putman putmanb at georgetown.edu
Mon Nov 9 12:51:17 EST 2015



On 11/9/15 12:12 PM, Wessel, Keith wrote:
> Reserecting this old thread to report a config bug or possibly just a mistake on my part.
>
> I added the Dolumn element to my LDAP data connector definition and got an error from the IDP on configuration load. Seems the XML schema doesn't like my ldapProperty elelements after my column element. If I move the column element to the end of the LDAP data connector block, though, all is well. Is this a bug? If so, I'd be glad to report it, but I wanted to make sure I'm not doing something silly first.

No it's not a bug.  LDAPProperty must appear before Column. 

In most/all of the attribute resolver schemas, the config child
elements are defined using a <sequence>, so in an instance document
they have to appear in the order defined in the schema.  A link to the
v3 data connector schema is below.  Look for the LDAP one, and you'll
see the required ordering of its child elements:

http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-schema/src/main/resources/schema/shibboleth-attribute-resolver-dc.xsd?view=markup


I don't know off-hand what sort of docs we have in the wiki on this,
but the actual XML schema files are always the authoritative source.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151109/eddc80c4/attachment.html>


More information about the users mailing list