My MFA script is clearing the list of requested attributes

Cantor, Scott cantor.2 at osu.edu
Sat May 27 12:28:54 EDT 2017


On 5/26/17, 2:44 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

> Thanks, Scott. But I'm still a bit foggy on this.So because I'm resolving all attributes from the request in the script, they're not
> being later resolved?

The resolution in the script shouldn't have any impact on the resolution that normally happens. I haven't received any reports of any undesirable interactions there, but it's possible that if the AttributeResolutionContext isn't removed (as the example does) there's something I haven't considered.

> From what you said, the later resolution should be unphased by my script even though I'm unnecessarily resolving everything.

I didn't know you were resolving "everything" but no, that shouldn't cause any problem.

> And if I do just want to resolve the single attribute, can you point me to a code snippet to accomplish that? I assume I still
> initialize an attribute resolution context and set the principal, but my call to resCtx.getRequestedIdPAttributeNames() would
> need to change. I assume I need to initialize a blank collection of attribute names that I can then call add or set on.

There's already an empty collection created, you just do:

resCtx.getRequestedIdPAttributeNames().add("allowedLoginMethods");

(That's taken from the example.)

-- Scott




More information about the users mailing list