What's new in Customer Journeys?

Connect and learn more!
What are implications of SESSION_HARD_TIMEOUT when using SSO? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

What are implications of SESSION_HARD_TIMEOUT when using SSO?



Questions about client timeouts and SSO

Content (required):

We recently moved to SSO. Users are reporting that they are timing out and losing their data. I have a couple questions about how the timeout config settings work.

1) CLIENT_SESSION_EXP - I understand that this relates to inactivity. If you are inactive beyond this value, you will need to log in again. There is a note in the documentation that states that when using SSO, you will not have the opportunity to reenter your password and will lose your data. Does this same behavior apply when you reach the SESSION_HARD_TIMEOUT? For us this is set for 4 hours. The documentation states that you get a 5-minute warning to reauthenticate and after that you lose your data. If using SSO, will you always

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!