Jose,

> I mean, if the TGT is not stored anywhere and you need to access a
> service that you didn't access before and you don't have an ST for,
> you'll get asked for username/password again (or the ST won't validate
> for the second service if you're not using the login form)

I see what you meant now. :-)  In the current version of the application,
the web service client first authenticates and gets a TGT (actually, it
gets a PGT/PTGIOU) and then gets an ST (actually, it gets a PT) before each
call to additional web services.  But once the executing of that client
ends, the TGT/PGT is lost, even though that TGT/PGT is still valid as
far as CAS is concerned (until CAS expires it).

Unfortunately, we'll have to support this authentication mechanism for a
while, but in the new version of the application, we won't be proxying, so
we'll be returning TGTs and STs to the web service client instead of
PTG/PTGIOUs and PTs.

Thanks again,

Pat


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