Increase inactivity timeout

I’m beating a somewhat dead horse, but… We would like to extend the session and token timeout/expiration of the 30/3 days rule (or at the very least bump up the inactivity timeout from 3 days to a total of 30 as well).

This has been asked many times before (in a total of 7-8 topics; I’ll link only a couple for reference):

The reoccurring theme with each is that the session expiration can be moved to a duration of 30 days, BUT the non-configurable inactivity timeout would make this redundant, seeing as the user would be logged out after 3 days of inactivity.

@jmangelo brings up some secret/potential/theoretical plans to provide auth0 users a way to configure expirations/timeouts:

I can let you know that there are plans to give you more control and flexibility over the session in question which would likely meet all your requirements, but at this time there is not yet definitive information about this.

However, the information I have is that we may want to provide something completely different then just a value setting, for example, a way to define a policy that would evaluate when the session could be reused or considered no longer valid. The side-effect of being more flexible is that it will require more time and meanwhile if just another setting was available it would be another thing that in future could require a migration.

As others in the linked threads, I’m all for a more flexible approach. However, I hope that auth0 realises that I can’t do much with promises today.

On June 17 @jmangelo wrote that he brought up the issue of extending the inactivity timeout - since I cannot comment under any of the threads linked (they’re all closed) -
I’ve created this topic to ask about it here.

We’d really appreciate:

  1. Increasing/lifting the limit of inactivity timeout (at least until the flexible ruleset has been implemented)
  2. Letting us know of any potential workarounds that would not break our SPA / API stack
  3. Giving us a somewhat definitive timeline on the flexible features that have been hinted at

- Counting on auth0’s understanding nature


Thank you for the feedback @ajv, we are always looking for ways our customers use and how they would like to see it grow. I would highly recommend sharing these details over at Auth0: Secure access for everyone. But not just anyone. so the request can be further documented. Thanks again!

Thank you James for the quick response.
However, there’s currently no answers to any of my questions?

I did as recommended and also wrote a similar submission to the feedback form, but I do believe this topic deserves a more worthy reply.

1 Like

Please keep in mind that not every employee might be knowledgeable about what is happening with a particular product request. Ultimately, the feedback form ensures that Product Managers like myself can see your particular feature requests and respond appropriately.

So to the specific questions:

  1. We are working to increase the inactivity timeout limit and define what that will look like. We spent a lot of effort this year in rearchitecting the underlying session management and SSO infrastructure so that we could handle this and other session related features. Before fully enabling this capability for all cloud customers we still have some additional engineering and product work to ensure that we don’t negatively impact reliability, and that we know exactly where this feature falls in our overall product portfolio.
  2. I am not aware of any workarounds for the current session limits.
  3. We are not ready yet to provide a definitive timeline on when this feature will be delivered. I know it is frustrating as a customer to not be able to deliver the User Experience you want in your apps due to a limitation of a service vendor. As the product manager who owns this feature, I share your frustration, as this is not the experience I want you to have. Please bear with us as we work to bring a significantly improved session management capability to our products.

Thanks for addressing the points I brought up. I hope the previous (and any potential future) queriers will now find their answers as well.

I eagerly look forward to the release of the new infra and wish your team all the luck in succeeding to deliver it.

PS! Could you provide a very rough/round ETA?
Nothing to quote later, but is it (currently) planned to be released this year? Q1/Q2 next year?

1 Like

We are currently working on priorities for 2019 with different engineering teams and until that is done there is no rough ETA to provide.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.