Most of my client's applications expect the email address as the
username, so our CAS implementation is set up to do this.  However, some
expect a unixish uid, and we would like to CASify those applications. 
Each row in custom authentication database that's behind our CAS
implementation contains both the email address and the uid, so it's easy
to convert from one to the other.  (The login web form always takes the
email address.)

We'd like to have CAS return either the email or the uid based on the
service id.  I thought I had it figured out, but I discovered that the
TicketGrantingTicketImpl class always returns the username that was
first used to authenticate.  If the user tried to access an application
that required the other username form, it would fall apart.

Since I can neither extend TicketGrantingTicketImpl nor create an
alternative implementation of TicketGrantingTicket (which I'd prefer),
is there a different way to approach this problem?

Thanks,
Rich
-- 
Richard J. Renomeron, Project Lead
TCG
Yes, it /can/ be done!
Tel: (202) 742-8460
Fax: (202) 986-5532
Email: [email protected]
AIM: rrenomeronTCG
www.tcg.com <http://www.tcg.com>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to