Question about Scripted attribute in attribute-resolver.xml

[Emilie Boulard]

Ok, thanks a lot. I see now where i took the wrong direction!


----- Mail original -----
De: "Cantor, Scott via users" <users at shibboleth.net>
À: "Shib Users" <users at shibboleth.net>
Cc: "Scott Cantor" <cantor.2 at osu.edu>
Envoyé: Vendredi 1 Mars 2024 14:40:39
Objet: Re: Question about Scripted attribute in attribute-resolver.xml

> Maybe i have restricted my domain search a bit too much in my 
> idp.attribute.resolver.LDAP.baseDN because i configure it to just acces the
> OU "people" and the OU "GroupPosix" is not included in that. This is why
> when i tried to made another DataConnector i configured a
> idp.attribute.resolver.LDAP.baseDN2.

You can, but you don't have to use properties to do any of that, and it will make it all more confusing to you initially to do that.

Just work with the connector alone and if it works and you want to pull details back out into properties, do it afterwards.

But yes, you need a different base DN, and you need to use an out of the original connector to build up the filter for the new one. What you can't do, so far as I know, is make the base DN itself dynamic based on the data.

-- Scott


-- 
For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net