IDP Attribute Query
Chad La Joie
lajoie at shibboleth.net
Mon Feb 27 17:28:46 GMT 2012
As Scott said, that's what the PrincipalConnector is for. So, if you
follow Francesco's approach whatever the incoming name identifier value
is, is going to be registered as the principal name. If you write you
own then the principal name will be whatever it returns.
I'll note though that there is nothing special about the principal name
with in the resolver. It happens to show up in logs but nothing within
the resolver really cares about it. So there is no reason to prefer it
over something the resolver looks up based on it. In fact, in IdPv3
there isn't even a special means of accessing it. It's just an
attribute like any other.
On 2/27/12 10:26 AM, James Drews wrote:
> Ok, so going down this line, is there then a way to asssign
> $requestContext.principalName
> to be the naming attribute of the second IDP so all the other attributes
> lookup correctly?
More information about the users
mailing list