> From what I understand I need to create a new > CredentialsToPrincipalResolver that will consider the Service as well > to resolve the Principal.
Nope. The principal is only resolved once from credentials on authentication. Afterwards, the same principal netid is sent to the application. > However I'm not sure whether I can findout > the service requesting authentication. You can, if you implement your own CredentialsBinder that let you bind a Credential from the HttpServletRequest. But it won't solve your problem because of above... For your problem, I would rely on principal's attributes to store the aliases of the principals and use a specific ServiceValidateController to use the particular alias depending on the /service/ of the application.... Romain Sudirikku Mohanjith a écrit : > Any help? > > /Mohanjith > > On Wed, Apr 23, 2008 at 2:05 PM, Sudirikku Mohanjith <[EMAIL PROTECTED]> > wrote: >> Hi, >> I want the Principal (specifically id) to be different depeding on the >> Service requesting authentication. This need is because we have 3 >> services(web applications) that we want to use CAS for authentication, >> but some users have different usernames for the 3 services. We plan to >> allow the users to claim the accounts and use one set of credentials >> to authenticate against CAS and then CAS will present different NetIds >> depending on the service. Hope I'm clear. >> >> From what I understand I need to create a new >> CredentialsToPrincipalResolver that will consider the Service as well >> to resolve the Principal. However I'm not sure whether I can findout >> the service requesting authentication. >> >> Any help is appreciated. >> >> Cheers, >> Mohanjith >> > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
