Usage of LDAPPROPERTY in attribute-resolver.xml

[Cantor, Scott]

On 8/14/14, 5:34 PM, "Farzan Qureshi" <fqureshi at rosmini.school.nz> wrote:

>It says that to convert the AD records to binary when they are fetched by
>Shibboleth, we have to add an LDAPPROPERTY. For example:

If that's their example, it's wrong.

><LDAPProperty name="java.naming.ldap.attributes.binary"
>value="objectGUID"/>

Unless the default namespace is set to the data connector namespace, you
need a dc: prefix on the element.

>When I add the above configuration in attribute-resolver.xml and restart
>tomcat services I get following errors.

Read the error. It's telling you the mistake.

>Caused by: org.xml.sax.SAXParseException; lineNumber: 345; columnNumber:
>78; cvc-complex-type.2.4.a: Invalid content was found starting with
>element 'LDAPProperty'. One of
>'{"urn:mace:shibboleth:2.0:resolver:dc":ReturnAttributes,
>"urn:mace:shibboleth:2.0:resolver:dc":LDAPProperty,
> "urn:mace:shibboleth:2.0:resolver:dc":StartTLSTrustCredential,
>"urn:mace:shibboleth:2.0:resolver:dc":StartTLSAuthenticationCredential,
>"urn:mace:shibboleth:2.0:resolver:dc":ConnectionPool,
>"urn:mace:shibboleth:2.0:resolver:dc":ResultCache}' is expected.

See the namespace in front of the LDAPProperty element in the expected
content list?

See how the "starting with" line doesn't have that?

-- Scott