You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have implemented SSO/SAML for an On-Prem JIra Core 7 installation using Okta's instructions. When attempting the enable the provisioning section in Okta, I am prompted to test the API credentials to Jira. I receive an internal server error 500 for a response. Doing an internal curl command with the username/password, I am able to verify the credentials are valid.
Working with Okta, they have view my configuration and believe it to be set up correctly, according to their instructions. Has anyone else ran into this issue?
John,
Sounds like something the Okta team should help you with.
Perhaps you could attach some more information? Screenshots or parts of the log file.
Cheers,
Lars
I've experienced the same issue & restarted our Jira instance. That seemed to fix the issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I also got the 500 response when testing my API credentials. My issue ended up being a missing DNS entry for the test Jira server I was using.
Okta needs to be able to resolve the DNS name you're using, and it needs to do so from the public Internet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.