CODEWITHSUNDEEP
jenkinssamlauth0
machzqcq
machzqcq

Reputation: 1029

Jenkins integration with Auth0

I posted the question already on the jenkins saml github repo, however not sure where is the exact cause of issue - https://github.com/connectifier/jenkins-saml-plugin/issues/9. Any help is appreciated

Auth0 Configuraiton

  1. Created an app "Jenkins"
  2. Under Jenkins app > Settings, the field "Allowed Callback URLs = http://52.34.126.192:8080/securityRealm/finishLogin" (I am using AWS , so that ip might change)
  3. Scroll down by clicking "Advanced Settings" . Under Endpoints > SAML, copied the URL "SAML metadata URL" and pasted in browser. It downloaded an XML file . We will use this later on jenkins side
  4. Had an Auth0 user "[email protected]" with connection "username-password-Authentication" database

I expect that after integration , I should be able to login to Jenkins with "[email protected]"

Jenkins Config

  1. Installed SAML plugin -https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin
  2. Enabled global security , then SAML , pasted the above XML file (step 3 above) into field "IdP MetaData", selected "Role based strategy" radio and hit save

image

  1. No effect will be observed now as it is mentioned in SAML plugin that Anonymous has to be disabled before seeing changes.
  2. Go to Manage and Assign roles, and then uncheck any box for anonymous (since if Anonymous is enabled, then auth will be bypassed)
  3. As soon as you hit save, you will be redirected to the Auth0 Login page (you can customize the login page on auth0, for now I went with defaults)
  4. Now I login with the Auth0 user that I created in Auth0 config

I get the error as below

image

LOGS

On the Auth0 side, the logs say that the user successfully logged in

image

Any help or thoughts are highly appreciated. Since Auth0 login says successful, I am posting this here, instead of Auth0 bugs

Upvotes: 5

Views: 3078

Answers (1)

madmuffin
madmuffin

Reputation: 993

This error seems to occur, when you do not explicitly set the audience setting in the auth0 SAML2 AddOn to the callback URL.

Setting it explicitly fixed the issue for me.

Screenshot

My guess: it is somehow related to the fact that the plugin uses a rather dated version of the pac4j libraries.

Upvotes: 5

Related Questions