Bug #7994
closed
Set token_duration to 6 hours instead of one hour
Added by Lukas Zapletal almost 10 years ago.
Updated over 6 years ago.
Description
During OpenStack provisioning on Dell hardware, it was reported that installation took longer than one hour. It was perhaps a remote site with slower connection, I haven't investigated.
I think new default value which is still sane could be six hours which "ought to be enough for everybody". Since this is not big deal (tokens are UUID, safe enough) I propose to set this as in Subject.
Discuss.
- Related to Bug #7995: Unable to escape build mode for hosts with expired tokens added
- Status changed from New to Ready For Testing
- Target version set to 1.7.2
- Pull request https://github.com/theforeman/foreman/pull/1865 added
- Pull request deleted (
Just for the sake of clarity why this was merged - 6h = 21600s.
In the outlandish event someone managed to make 1M requests per second without blowing up the smart proxy, that makes 2.16*10^10 possible checkups to brute force it, there are about 3.4 × 10^38 possible UUIDs.
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 21
- Bugzilla link set to 1166167
- Category set to Settings
- Assignee set to Lukas Zapletal
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by