Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: saml-plugin
-
Labels:
-
Similar Issues:
Description
Using an API token configured for a user doesn't allow access to the api e.g. accessing https://user:apitoken@jenkins/crumbIssuer/api/json causes a redirect to the saml auth provider instead of authenticating with the users apitoken.
Attachments
Activity
so it is resolved, right?
Yes, sorry for the noise
James Sharpe
added a comment - Yes, sorry for the noise I'm facing the same issue. Its redirecting to the SAML Auth Provider instead of authenticating with the username and api token. Am on 2.179
Vinay B
added a comment - I'm facing the same issue. Its redirecting to the SAML Auth Provider instead of authenticating with the username and api token. Am on 2.179 Vinay B see the James comments, the user has to login at least once to grab the groups and create the user, also it should be a SAML real user.
I've just regenerated the tokens under a user that authenticates with saml and it works now. The user for which it was failing was a user that wouldn't be authenticated via saml and was probably using a legacy api token.