Conditioned attribute
Rod Widdowson
rdw at steadingsoftware.com
Mon Jul 8 10:13:58 UTC 2024
> I can see that myLDAP produce these attributes
So, you see a log from net.shibboleth.idp.attribute.resolver.impl.Attribubute Resolver
"Data connector <id> resolved the following attributes: ..... "
And that includes "uid" and "displayName"?
That code is so mainline if you are seeing that log message but not the attributes during filtering then something strange is happening.
But this
<AttributeDefinition xsi:type="Simple" id="pager" preRequested="true">
<InputDataConnector ref="myLDAP" attributeNames="pager"/>
</AttributeDefinition>
Feels weird to me. Attribute names are in a flat name space, what you are doing is defining the an attribute with the same name as the thing that the data connector used. That makes my head hurt and actually I am surprised that the resolver didn’t detect a circularity. It would probably be a simplification if you separate the name of the preRequested Attribute from the data-connector product attribute. I have no idea if this is your problem but it will make life easier for others reading your configuration.
Rod
More information about the users
mailing list