attribute resolution during the login process

[Paul Hethmon]

I have a need to resolve some attributes after the user has been authenticated but prior to releasing control back to the profile handler in the Multi-Context Broker. I have to get a list of allowed authentication contexts for a user to see what they are allowed to use. So instead of defining yet another attribute mechanism, I would like to pull in the attribute resolver and have it do the job for me. After walking through code and configuration files for the last day, I'd like to see if this seems reasonable:

1. Get a handle to the attribute resolver service from the servlet context
2. Create necessary data structures the attribute resolver needs
3. Let it resolve the attributes for the principal
4. Pull out what I need
5. Complete the authentication process

So is getting that handle to the base service and using it the right way to go?

This is for v2.

thanks,

Paul


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20130801/76073b84/attachment.html