jenkinsci
Allow System Authentication Through Username/Password
What feature do you want to see added?
GitLab plans to completely phase out API tokens / Personal Access Tokens by version 16. Many distributions of GitLab already have all forms of access tokens removed. A way to access GitLab from Jenkins in the system configuration utilizing username / password will be needed, and is currently needed. The current setup for this plugin only allows authentication through the Personal Access Token credential type.
Upstream changes
No response
GitLab plans to completely phase out API tokens / Personal Access Tokens by version 16
Is this true? The only information I could find about this states that access tokens must have an expiry date starting with GitLab 16. But there is nothing stopping you setting the expiry date 20 years into the future.
GitLab plans to completely phase out API tokens / Personal Access Tokens by version 16
Is this true? The only information I could find about this states that access tokens must have an expiry date starting with GitLab 16. But there is nothing stopping you setting the expiry date 20 years into the future.
Apologies, a bit of truth and rumors got mixed up. Previously, around when I made my post, tokens had been removed from FIPS GitLab entirely. See the note about FIPS here.
When speaking with a GitLab representative trying to assist us back then, they implied that tokens may get removed from GitLab all together by version 16.
Thankfully, tokens have been added back to FIPS since then, so I think all my fears of tokens being completely removed are gone, for the time being at least.
update: as of GitLab 17 access tokens have a forced expiration date of one year for standard accounts
but unlimited expiration is still available for special "service accounts"
