CAS SSO fails for External ticket repository post restart of CAS server

91 views
Skip to first unread message

Casseora

unread,
Sep 25, 2018, 10:01:15 AM9/25/18
to CAS Community
Currently i am using apereo CAS 5.2.1 . 

I am  using redis as ticket repository . 

SSO works fine if the server instance is not restarted . 

Post restart even providing the same TGC value the server fails to perform SSO and ask for credentials. 

Redis conf :

cas.ticket.registry.redis.host=localhost
cas.ticket.registry.redis.database=0
cas.ticket.registry.redis.port=6379
cas.ticket.registry.redis.password=
# cas.ticket.registry.redis.timeout=2000
# cas.ticket.registry.redis.usePool=true

cas.ticket.registry.redis.pool.max-active=20
cas.ticket.registry.redis.pool.maxIdle=8
cas.ticket.registry.redis.pool.minIdle=0
cas.ticket.registry.redis.pool.maxActive=8
cas.ticket.registry.redis.pool.maxWait=-1
cas.ticket.registry.redis.pool.numTestsPerEvictionRun=0
cas.ticket.registry.redis.pool.softMinEvictableIdleTimeMillis=0
cas.ticket.registry.redis.pool.minEvictableIdleTimeMillis=0
cas.ticket.registry.redis.pool.lifo=true
cas.ticket.registry.redis.pool.fairness=false

cas.ticket.registry.redis.pool.testOnCreate=false
cas.ticket.registry.redis.pool.testOnBorrow=false
cas.ticket.registry.redis.pool.testOnReturn=false
cas.ticket.registry.redis.pool.testWhileIdle=false

cas.ticket.registry.redis.crypto.signing.key=
cas.ticket.registry.redis.crypto.signing.keySize=512

cas.ticket.registry.redis.crypto.encryption.key=
cas.ticket.registry.redis.crypto.encryption.keySize=16

cas.ticket.registry.redis.crypto.alg=AES

 Ticket Conf :

cas.ticket.tgt.hardTimeout.timeToKillInSeconds=28800
cas.ticket.tgt.throttledTimeout.timeToKillInSeconds=28800
cas.ticket.tgt.throttledTimeout.timeInBetweenUsesInSeconds=5

cas.ticket.tgt.maxTimeToLiveInSeconds=28800
cas.ticket.tgt.timeToKillInSeconds=7200
cas.ticket.tgt.onlyTrackMostRecentSession=true
cas.ticket.tgt.maxLength=50
cas.ticket.tgt.rememberMe.enabled=true
cas.ticket.tgt.rememberMe.timeToKillInSeconds=28800

cas.ticket.st.timeToKillInSeconds=7200
cas.ticket.st.numberOfUses=1

Any help is highly appreciated .

Thank you in advance 

Ray Bon

unread,
Sep 25, 2018, 12:28:08 PM9/25/18
to cas-...@apereo.org
You can check the contents of redis with the redis command line tool, https://redis.io/documentation.
Do you have the signing and encryption keys for redis and the tickets in the confing file? If not, they will be generated on each start.

Ray
-- 
Ray Bon
Programmer analyst
Development Services, University Systems
2507218831 | CLE 019 | rb...@uvic.ca
Reply all
Reply to author
Forward
0 new messages