We are trying to implement SAML SSO so that our customers don't need to sign-in in the customer portal. I'm currently testing the setup of SAML in a free trial Jira Service Management I've created (https://yummyteh.atlassian.net) also with a free trial of Atlassian Access.
We've already enabled and setup the SAML configuration under Security tab in Atlassian Admin and also enforced SSO for 1 user in Authentication Policies. We've also created a custom policy in Azure AD B2C that uses SAML2 protocol. This is the link we're using for an Identity Provider initiated SAML sign-in (https://swapoolabsdev.b2clogin.com/swapoolabsdev.onmicrosoft.com/B2C_1A_BASIC_SIGNIN_SAML/generic/login?EntityId=https://SwapooLabsDEV.onmicrosoft.com/atlassian-saml-test&RelayState=https://yummyteh.atlassian.net/jira/servicedesk/projects/CS/queues/custom/1)
But when we're trying to sign-in a test account we're getting a 404 to this HTTP request (https://swapoolabsdev.b2clogin.com/swapoolabsdev.onmicrosoft.com/B2C_1A_Basic_SignIn_SAML/client/perftrace?tx=3be1fd6b-4ed4-42b9-b257-bd31fadfdcfc&p=null)
This is the documentation we're following (https://docs.microsoft.com/en-us/azure/active-directory-b2c/saml-service-provider?tabs=windows&pivots=b2c-custom-policy#next-steps). I hope someone can help us, thanks in advance.
Hello @Christopher Villaran,
Welcome to the Atlassian Community!
When it comes to using SAML, currently, it’s not supported to use it on the customer portal.
SSO will only work for users with an Atlassian account, so in case you need customers to log in using SSO, they must have an Atlassian account (internal user without application access) and use the same URL as internal users to login (xxxxxxx.atlassian.net instead of xxxxxxx.atlassian.net/servicedesk/customer/portals).
and also enforced SSO for 1 user in Authentication Policies
Is it working normally for the internal user?
But when we're trying to sign-in a test account we're getting a 404 to this HTTP request
Is the test account an internal user from the same domain that was verified?
Thank you for the details, @Christopher Villaran.
I see that the email is being redirected to that page and it shows an error that points to Azure AD B2C and it seems to be a configuration problem on their side:
I found this documentation that might help, but I would like to share that when setting up SAML with Azure, the documentation that contains the steps is the one below:
The documentation you are following is not from a native integration. The one above is one where Atlassian worked with Azure to have a specific template.
Please, take your time to go through that documentation and let us know if you have any other questions.
Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events