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


Sounds like something the Okta team should help you with.

Perhaps you could attach some more information? Screenshots or parts of the log file.




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 Join to answer
Community showcase
Alexey Matveev
Published Saturday in Jira

How to run Jira in a docker container

Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...

129 views 3 5
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot