Sorry, a communication error occurred while trying to contact the remote authentication server..

Hi ,

I have installed ldap certificate properly an I am not able to login to JIRA. Below is the error message I received.

Please help me. Could there be any network issue here ?

6.4.14 - the current JIRA version we are using.

Attached is thLog-Communication Error.JPGe log file screenshot.

##########################################################

Thanks,
Nav

1 comment

If you have installed the certificate correctly, then the error message is telling you that it's not valid for accessing your LDAP server.

Here is the screenshot for the same

 

ldap cert.jpg

I can't tell you what you've got wrong in your certificates - I don't know what your server is requiring of them, or how they were generated.

But, I do know the certificate is wrong, and I'd guess it is probably self-signed.  I would expect that error message to happen because the certificate does not conform to RFC 2818, which Java insists on handling strictly.

You may want to talk to your certificate authority about:

 

 RFC 2818:

If a subjectAltName extension of type dNSName is present, that MUST be used as the identity. Otherwise, the (most specific) Common Name field in the Subject field of the certificate MUST be used. Although the use of the Common Name is existing practice, it is deprecated and Certification Authorities are encouraged to use the dNSName instead.

[snippy as not needed]

In some cases, the URI is specified as an IP address rather than a hostname. In this case, the iPAddress subjectAltName must be present in the certificate and must exactly match the IP in the URI.

Hi Nic,

Articulated the whole scenario in few steps. Please dont mind.(this is to give a clear picture to you on what happened exactly)

Well, this is the same certificate I am using which worked fine 10 days back.

Below is the overview of the things I did few days back, which will give you some idea on what has happened.

Our goal is to upgrade the current version of JIRA(6.3.12) to latest available version.

A DEV environment is been created and given to me to have the complete cycle ready(6.3.12 to 7.3.X)

1. Replicated the same environment(6.3.12) of JIRA from PROD to DEV.(PostgreSQL to Oracle 11g) using XML Backup.

2. Upgraded 6.3.12 to 6.4.14

3. Informed DBA to manually migrate data from 11g to 12c(as 6.4.14 supports both 11g and 12c)

4. Used the same ldap certificates during the step-1 and it worked fine.

5. Due to some issues in Confluence, I requested my linux admin to remove the Confluence user. But by mistake he removed JIRA user instead of Confluence user.

(Till here I was able to login with the LDAP use creds, as I have implemented them in the 1st step)

6. As I was not able to proceed with 7.0 upgrade(JIRA user missing), I have completely wiped out everything from the application server and restarted installing 6.4.14 directly on to the server.

7. As I have the 12c database available with the data, I have installed 6.4.14 and able to connect to the database.

8. When I used "keytool" to authenticate LDAP users(screenshot shared earlier), I have been thrown with this error.

(Sorry, a communication error.......)

 

Thanks,

Navadeep

Comment

Log in or Sign up to comment
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Amir Kazemi
Posted 3 hours ago in Jira

We want to know what Jira Service Desk apps you're using!

Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...

15 views 0 3
Join discussion

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