Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira socket issue after Integration with Okta for Single Sign On

Integrated Jira On prem with OKTA and when accessing Jira its redirecting to OKTA and once we enter the credentials, we are getting "Site cannot be reached".

In logs, we could see " connect timed out"

Any idea?

Thanks in Advance.

1 answer

Hi @Shruthi BM ,

It seems like there is some issue while processing the response from OKTA and it would be great if you can share detailed logs from atlassian-jira.log file to troubleshooting this issue.


Also, can you please let me know which SSO app are you using to configure Single Sign-on between JIRA and OKTA? You also can take a look into one of the SAML SSO apps from Atlassian Marketplace.


Step by Step guide to configuring the app with OKTA


Feel free to reach out to miniOrange support in case if you need help with the SSO configuration.




I work for the miniOrange. One of the top SSO vendor in the Atlassian Marketplace. 

Thanks Lokesh for your response.

I have integrated directly Jira on prem with OKTA and in the logs i am just seeing sockettime out error. No much information in the logs.

SSO is working as i am getting redirected to OKTA when accessing JIRA directly and after entering the credentials i am getting "Site cannot be reached".

If i run the ping command, i am getting response.

Hi @Shruthi BM ,


Are you using JIRA Datacenter and its inbuild SAML Support? Is it possible to share the Single Sign-on URL and SP Entity ID/Issuer configured in OKTA SAML APP?




Hi Lokesh,

I integrated using Atlassian Jira which is available in OIN in OKTA and hence i am not seeing above information.

When i click on View setup instruction from OKTA, i could see some configurations to be done in JIRA which i completed and after that only i am getting an error.

OKTA logs says authenticated successfully.

Hi @Shruthi BM ,


It looks like JIRA is unable to process the SAML Response from OKTA within the time period. I recommend you to reach the Atlassian Support Portal and provide the team with your application log files to troubleshoot this issue.


In the meantime, you can try a third-party SAML SSO app from Atlassian Marketplace.




Thanks a lot Lokesh.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

89 views 3 8
Read article

Community Events

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

Events near you