Hi

I am using an AuthenticationMetaDataPopulator to feed the CAS ticket with some 
extra information : the uid of the user which in my case is not the same as the 
login...

Since a little while (I can't exactly guess when) things gone awry.

I can trace that the actual AuthenticationMetaDataPopulator is called by the 
login flow and the authentication attributes are feeded with the uid.

Latter when I validate a proxy ticket with a third party application, the 
ticket returned by the CAS server (which is authenticated) does not contains 
the uid attribute.

Did I miss something ??


-- 
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

Reply via email to