Requested Attributes on IdPv3

[Simon Gfeller]

>
> >I try to configure an IdP 3.2 so, that the IdPs Attribute Resolver tries
> to resolve only the requested attributes from the relying party and NOT all
> attributes from the attribute definitions like now.
>
> Filtering happens at the end, it is not part of the determination of what
> to resolve. You would have to code a custom activation condition to attach
> to the resolver plugins that actually did all the work of looking at the
> metadata.
>

OK, but is there another solution without metadata to determine what is to
resolve?  With the AuthnRequest from the SP for example?

I think there must be a solution, because I looked into the source code of
the IdPs Attribute Resolver implementation. In the
AttributeResolutionContext is the following field:
    /** (internal) Names of the attributes that have been requested to be
resolved. */
    @Nonnull @NonnullElements private Set<String> requestedAttributeNames;

And because this set is always empty on my IdP, the AttributeResolverImpl
class tries to resolve all attributes.
The question is, from where the IdP should get these attribute names?

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