Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
- Shib sessions implicitly establish CAS sessions, but not vice versa.
- Implications:
- If you first log into Shib (say for Gmail), you can later seamlessly SSO to CAS sessions.
- First logging into CAS will not seamlessly SSO to a Shib session.
- Successful authentication to Shib grants user a Ticket Granting Ticket (TGT) to be used for SSO.
- TGT idle timeout: 2 hour sliding window.
- TGT hard timeout: 8 hours from date of TGT creation.
- Each application maintains its own session state.
- Successful authentication to CAS grants user a Ticket Granting Ticket (TGT) to be used for SSO.
- TGT idle timeout: 2 hour sliding window.
- TGT hard timeout: 8 hours from date of TGT creation.
- Each application maintains its own session state.