Okta Provisioning and Jira API

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?

 

 

3 answers

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in United States

Administrators Cleanup

Good morning, After a long weekend cleaning up, I am still in the cleanup mode 😊. I am curious to know: When do you feel the urgency to cleanup your Atlassian Tools? How many times do y...

22 views 0 0
View post

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you