Raw attributes from a HttpServletRequest attribute?

[Brian Reindel]

If it helps I am using a custom login handler. It is my own remote user handler.

https://wiki.shibboleth.net/confluence/display/SHIB2/ResolverScriptAttributeDefinition#ResolverScriptAttributeDefinition-InformationAvailabletotheScript

Under "Information Available to the Script", those five interfaces
have various fields that are accessible from the script attribute
definition, one of which is the subject and then principals. As a part
of the remote user handler authentication I set the principal,
however, I'm not seeing how I could store extended data on it for use
in the attribute definition.


On Tue, Aug 6, 2013 at 7:31 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 8/6/13 5:10 PM, "Brian Reindel" <brian at reindel.com> wrote:
>
>>Is there a data connector or attribute definition that will pull me
>>back a value from a request attribute?
>
> Just the Scripted one, I suspect.
>
>>I can get that later with the PrincipalName attribute definition.
>>However, I want to set other attributes that came back as well (the
>>oauth token and verifier). If I do that, how can I then later access
>>them? They don't necessarily have to be request attributes. Is there
>>is an underlying context or Shibboleth session where I can set them in
>>order to access them later in the attribute resolver?
>
> Not without a custom login handler, and even then you're limited to
> front-channel attribute use during SSO and not queries. A custom login
> handler can store extended data in Principals attached to a Subject
> returned from the login handler (those being the Java Subject/Principal
> APIs).
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net