Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira single sign-on (SSO)

泉波 丁
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 22, 2023

I am developing an IAM application based on the SAML protocol, serving as an IDP for Jira single sign-on to enable single sign-on between our internal services and Jira. At present, I have followed the SAML protocol's flow and have arrived at the final step of sending the SAMLResponse to Jira's consumer URL. However, I have encountered an issue where Jira returns a 400 response code after I send the SAMLResponse, with no other error messages provided. Despite the absence of any error messages in the logs, I need to debug the problem to determine its cause. To resolve this issue, I recommend using suitable SAMLResponse debugging tools to validate whether the request complies with the standard and to ensure that the request includes the necessary parameters and attributes. Additionally, it is advised to check Jira's logs to obtain more information about the error.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events