Idea Details

Enhance SiteMinder so that using Security Zones with persistent sessions behaves the same as with n

Last activity 06-04-2019 11:56 AM
Alfred Macedo's profile image
04-15-2016 02:07 AM

Currently when using security zones you will have separate session cookies and if one zone cookie times out, it does not timeout additional zone cookies. Each zone cookie is able to maintain timeouts individually.

 

When you enable persistent sessions, only 1 entry is created in the session store even though you may have multiple zone cookies. When 1 zone cookie times out, the entry is expired in the session store. Now the next time SiteMinder has to validate a different zone's cookie, it will fail as the entry in the session store is expired or removed by housekeeping. This leads to an SMAUTHREASON=40 Failed to update persistent session in Session Services.


Comments

10-18-2018 10:49 AM

Thank you for your contribution of an enhancement idea to the CA Community. CA is continually working to improve its software and services to best meet the needs of its customers. Your input is vital to that effort. The CA Single Sign-On Product Management team has reviewed your suggested enhancement. Based on current roadmap priorities and/or the limited amount of community support for this idea over the last year (please see this document describing how we are reviewing ideas: https://communities.ca.com/docs/DOC-231170123), we are not accepting this idea into the product backlog. Therefore, it is being moved to a “Not Planned” status.   

05-31-2016 02:03 PM

Thank you for your contribution of an enhancement idea to the CA Community. CA is continually working to improve its software and services to best meet the needs of its customers. Your input is vital to that effort. The CA Single Sign-On Product Management team is reviewing your enhancement suggestion. The Community will continue to be able to vote on this enhancement idea.