If you've got them attached to the credential object you can manually add them to your principal attribute map (with a custom Resolver).
You'll then need to make sure the names match the ones that appear in the AttributeRepository That should allow them to be found. In theory.... I've never tried it. On Mon, Nov 8, 2010 at 2:09 PM, Marvin Addison <[email protected]>wrote: > > I have the following setting working well in my case - CustomCredentials, > CustomCredentialsToPrincipalResolver and a CustomAuthenticationHandler. I > have a tweaked casServiceValidationSuccess.jsp through which I do the > attribute release. > > We'll try to help, but you're in the land of the unsupported with that > approach. > > > Now my requirement is to (also) intercept login form request parameters > (lets say email or emp id) and release it back from attribute repository. > How can I do that? > > With a lot of hacks, I'd imagine. CAS simply lacks support for > querying the attribute repository from the login webflow. Attributes > are released in response to services authenticating from CAS, not from > user authentication. In any case you will need to substantially > modify the login webflow. The only further guidance I can provide is > that your extensions should come after user authentication/principal > resolution since the authenticated principal name would be required to > query the attribute repository. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
