Closed silviogutierrez closed 9 months ago
I suspected this, as the docs clearly state SESAME_MAX_AGE set to None means we have no timestamps of any kind.
But authenticate and get_user will still happily accept max_age=5 but this will be silently ignored.
authenticate
get_user
max_age=5
Not a huge issue, but given SESAME_MAX_AGE defaults to None, worth clarifying.
SESAME_MAX_AGE
Let me know if this makes sense and I can open a docs PR.
Thanks for all the great work on this library.
You're supposed to get a warning for this. Are you not seeing the warning?
You're right, I am. I must have missed it in all the server output.
Thanks again.
I suspected this, as the docs clearly state SESAME_MAX_AGE set to None means we have no timestamps of any kind.
But
authenticate
andget_user
will still happily acceptmax_age=5
but this will be silently ignored.Not a huge issue, but given
SESAME_MAX_AGE
defaults to None, worth clarifying.Let me know if this makes sense and I can open a docs PR.
Thanks for all the great work on this library.