sometime i get AD error while login and it does not allow to login

[Pareshkumar Gandhi]

error:

2014-07-22 09:26:28,545 http-bio-8080-exec-11 ERROR anonymous /rest/gadget/1.0/login [crowd.manager.application.ApplicationServiceGeneric] Directory 'Active Directory server' is not functional during authentication of 'abc'. Skipped.
2014-07-22 09:26:28,545 http-bio-8080-exec-11 ERROR anonymous /rest/gadget/1.0/login [jira.security.login.JiraSeraphAuthenticator] Error occurred while trying to authenticate user 'abc'

[Andris Grinbergs]

Hi, I had this or similar error when one of AD servers was unreachable (however it was listed in DNS). One of the possible solutions is to use exact IP of AD server instead of hostname when configuring user directory in Jira.

[Septa Cahyadiputra]

This is what I will do. Most of the time, DNS networking cause JIRA to try to connect to other URL. Changing it to IP will exclude DNS issue as the cause. However, this issue is easy to tell as the stack trace will describe the URL that it try to connect to, and if it is different with wath you configured, it is usually the cause of your issue.

[Paresh Gandhi]

I'm using IP address.

[Andris Grinbergs]

You may try to connect to AD on port 3268 instead of 389, it sometimes helps.

[Nic Brough -Adaptavist-]

That's quite clear - Jira is trying to authenticate and your AD server is not letting it in.

You should probably start by looking at the AD server logs - find out why it's refusing to let Jira in.

[Paresh Gandhi]

We have one more Jira instance which uses same ldap credentials where we never faced this issue ? Is there any issue if I connect multiple Jira to same AD.

[Nic Brough -Adaptavist-]

The only other thing it could be is a network issue - Jira is unable to reach the AD server (and the other one that always works has a better network setup)

Yes, you can connect as many Jiras as you need to AD.

[Paresh Gandhi]

I have to look at network setup of server machine or jira instance?

[Nic Brough -Adaptavist-]

The server.

Jira simply runs on a system, and if it needs to reach out to other systems like AD, it will ask the server for network information. The failure here is that the remote server doesn't seem to always respond, so it's the networking on the local server, the network or the AD server.