CAS5 Protocol diagram with OpenID Connect and CAS protocol mixed clients

[Yan Zhou]

Hello,

CAS has a nice diagram explains CAS protocol, how it achieves SSO, by using cookie. 

With CAS5, I can achieve SSO with two clients, one speaking CAS protocol, the other speaking OpenID Connect. 

How did CAS do that, is that by the use of cookie as well?  I do not think OpenID Connect itself uses cookie.  Any idea?

Similarly, if two clients both speak OpenID Connect, is cookie support still required for CAS to support SSO between them?

Thx!

Yan

[Ray Bon]

Yan,

CAS creates a TGC (ticket granting cookie) that it uses to look up the SSO session. It is (typically) not available to client application.

Ray

-- 

Ray Bon

Programmer Analyst

Development Services, University Systems

2507218831 | CLE 019 | rb...@uvic.ca

[Yan Zhou]

Yes, I know TGC, and it is in the cookie. 

How do two clients (native Mobile Apps) using Open ID Connect  talk to CAS, and achieve SSO? Where is TGC stored? There is no cookie in native apps. 

In other words, when user is authenticated in CAS via the first client, and he goes to the 2nd client app., what is the protocol look like that SSO is achieved?

Yan