How can I configuration SAML SSO in Keyclock to use atlassian cloud?
I got document to configure here
https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html
But Keycloak unsupported and document not have details enough to setting.
please help guide and show configure example.
Hi Thanapon,
We don't specifically support / test against Keycloak, so it's covered in the Unsupported identity providers section of our setup document. The details in that section apply in general to any SSO provider that supports SAML (which Keycloak does).
On the other side of the equation, you can follow Keycloak's own documentation for setting up a Client for Atlassian Access to use.
Cheers,Daniel
Start by creating a SAML client in Keycloak. Call it whatever you like because we'll be changing it later.
In the Keycloak client configuration, turn OFF "Client Signature Required" and click on "Save".
In Atlassian Access, you need to provide three values:
"Identity provider Entity ID" - this will be your server's URL followed by /auth/realms/<realm name>
"Identity provider SSO URL" - this will be your server's URL followed by /auth/realms/<realm name>/protocol/saml
"Public x509 certificate" - this can be obtained from Keycloak. On our server, I found in under Realm Settings - Keys, then clicking on the Certificate button.
With the values entered, Atlassian Access will give you two URIs - SP Entity ID and SP Assertion Consumer Service URL.
Edit the SAML client you created in Keycloak. Change the client ID to be the "SP Entity ID" value. Copy the "SP Assertion Consumer Service URL" and paste it into "Valid Redirect URIs" and "Base URL". Click "Save".
That should do it. Just remember that SSO only works for validated domains.
Hey @Philip Colmer ,
I can confirm that your user Guide works!
Thx a lot for sharing!
Cheers & best,
Andreas
Excellent, it worked for me too! @Daniel , could you please correct the documentation? The older general instructions and screenshots are wrong.
@Preston Lee i believe this message was not meant for me.
I just want to confirm that I managed to configure SSO from Atlassian Access to Keycloak version 21.1.2. Keyclock changes UI quite often..
I mostly followed instructions here, but also needed to configure some things not explicitly mentioned here:
I believe rest is mostly the same.
I have followed all the steps provided by @Philip Colmer and @mmrvelj but I am getting stuck with the following error upon redirect:
{"key":"badRequest","context":{"message":"Invalid customer saml login callback request","reason":"No In Response To in SAML Response"}}
Did anyone else face this issue and found a way around it?
It might be related to the keycloak issue #14055 but I am wondering, since everyone else got it running here, if there has been a change in the JIRA SAML Authentication Flow or if I am missing a setting somewhere.
Thanks in advance!
It looks like you're new here. Sign in or register to get started.
