You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, one important step before filing an issue is to share reproducible steps. This is exactly where we're having trouble with; the bug below only happens in production.
The issue is once we shorten the token_lifespan from 2 weeks to 30 minutes (or 1800). It gives users http 500s and failing to reset their passwords.
One idea is to set the lifespan to a specific user. So we can either isolate the bug and/or the fix before rolling it out to everybody else. If nobody has other ideas, How can we set different token_lifespan for a user with Devise?
Example of what we see in the prod logs:
NoMethodError: undefined method `[]' for nil:NilClass
args[:expiry] = tokens[args[:client_id]]['expiry']
^^^^^^^^^^
Hello, one important step before filing an issue is to share reproducible steps. This is exactly where we're having trouble with; the bug below only happens in production.
The issue is once we shorten the
token_lifespan
from 2 weeks to 30 minutes (or 1800). It gives users http 500s and failing to reset their passwords.One idea is to set the lifespan to a specific user. So we can either isolate the bug and/or the fix before rolling it out to everybody else. If nobody has other ideas, How can we set different
token_lifespan
for a user with Devise?Example of what we see in the prod logs:
Our configuration:
The text was updated successfully, but these errors were encountered: