Bug #7994: Set token_duration to 6 hours instead of one hour - Foreman

Bug #7994

Set token_duration to 6 hours instead of one hour

Added by Lukas Zapletal over 8 years ago. Updated over 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Lukas Zapletal

Category:

Settings

Target version:

1.7.0

Difficulty:

Triaged:

Bugzilla link:

1166167

Pull request:

https://github.com/theforeman/foreman/pull/1865

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

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 issues

Associated revisions

Revision c0262662 (diff)
Added by Lukas Zapletal over 8 years ago

Fixes #7994 - increased default token_duration setting

History

#1 Updated by Lukas Zapletal over 8 years ago

Related to Bug #7995: Unable to escape build mode for hosts with expired tokens added

#2 Updated by Lukas Zapletal over 8 years ago

Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1154730

#3 Updated by The Foreman Bot over 8 years ago

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 ()

#4 Updated by Daniel Lobato Garcia over 8 years ago

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.