Make JWT expirations configurable for GitLab Self-Managed
Context
You can use GitLab to publish and install Conan packages to your project or instance using a job token. The user must authenticate with the conan user
command prior to any operations with private packages.
The problem is that the authentication token expires too often, which makes it difficult to use. Originally the expiration was set to 1 hour and in #234005 (closed) GitLab bumped it to 1 day.
Problem to solve
Although it makes sense for GitLab to expire the JWT each day, there are Self-Managed customers that have been using Artifactory and using tokens that do not expire. This is resulting in the Developers at their organization to log in each day which is not efficient.
Proposal
Make the expiration window for GitLab job tokens configurable for Self-Managed instances. This would allow Admin to ease this restriction and allow their teammates to build and deploy code more efficiently.
Questions
Does it make sense to allow for this configuration globally or for specific features or both?