additional attributes after authentication

[Scott Battaglia]

Anand,

The first thing is to ensure that your CredentialsToPrincipalResolver 
returns a principal with that attribute.

 From that point, you have two options:
1. Modify the XML response so that it includes an additional attribute 
(which means you have to modify the CAS clients to be able to find that 
attribute). [this is easier to do in the CAS 3 client, but that hasn't 
been released yet]
2.  Modify the JSP page that generates the response to swap out the 
normal NetId for the personId when the service is the one that needs the 
personId.

The second one requires less effort but it also hardcodes a value into 
the JSP page (so if you ever had another app that needed that value 
you'd have to modify that page again).

-Scott

Anand Meher wrote:
>
> As usual, I will be using the user and password to authenticate with 
> CAS server and ldap, which returns netid.
>
>  
>
> However existing web application,  I am planning to casify is using 
> personid instead of netid.
>
> Personid is attribute in ldap.
>
> Any suggestion on how to return the personid after cas authentication 
> to this webapp.
>
> Thanks.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>