-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.426.1
Hello,
2 years back I created an API token for my account and I still, now, can use it with basic auth.
This API token is no more visible in jenkins UI.
In July 2023 we did an upgrade of Jenkins (from 2.375.2 to 2.401.2)
Starting from that date, all newly created API tokens are not working with basic auth. (401 unauthorized)
We now are in 2.426.1 version of Jenkins and we still have the same issue.
Example curl command which gives unauthorized 401 error:
curl --silent -u <username>:<api_token> https://jenkins/job/<jobname>/lastBuild/api/json
Update:
Looks like using the Azure object ID instead of UPN solves the issue for newly created API tokens.
But there are below concerns still: