Users cannot Login with Active Directory credentials after server reboot.

Reto Kämpfer

We rebooted the server that is hosting the Jira server local and now we cannot login with our AD credentials. The message is Username and password is wrong. We have looked in the log (atlassian-jira-security.log) and found this:

2020-12-30 11:54:20,258+0100 https-openssl-nio-8443-exec-5 anonymous 714x118x1 - 192.168.0.250 /secure/Dashboard.jspa HttpSession created [16dqcn3]
2020-12-30 12:34:31,876+0100 https-openssl-nio-8443-exec-20 anonymous 754x183x1 - 89.247.124.152 /secure/Dashboard.jspa HttpSession created [1vnifdw]
2020-12-30 12:54:50,423+0100 ContainerBackgroundProcessor[StandardEngine[Catalina]] HttpSession [16dqcn3] destroyed for 'anonymous'
2020-12-30 13:07:05,282+0100 https-openssl-nio-8443-exec-7 anonymous 787x311x1 - 192.168.0.63 / HttpSession created [112j09n]
2020-12-30 13:14:50,122+0100 https-openssl-nio-8443-exec-10 anonymous 794x352x1 - 192.168.0.250 /secure/Dashboard.jspa HttpSession created [1yk8m5d]
2020-12-30 13:15:44,256+0100 https-openssl-nio-8443-exec-14 anonymous 795x371x1 - 192.168.0.250 /secure/Dashboard.jspa HttpSession created [1934a64]
2020-12-30 13:24:20,737+0100 https-openssl-nio-8443-exec-18 anonymous 804x414x1 - 192.168.0.250 /secure/MyJiraHome.jspa HttpSession created [xoatsv]
2020-12-30 13:34:52,371+0100 ContainerBackgroundProcessor[StandardEngine[Catalina]] HttpSession [1vnifdw] destroyed for 'anonymous'
2020-12-30 13:41:52,694+0100 ContainerBackgroundProcessor[StandardEngine[Catalina]] HttpSession [43kb4r] destroyed for 'anonymous'
2020-12-30 13:51:35,607+0100 https-openssl-nio-8443-exec-10 anonymous 831x492x1 - 192.168.0.250 / HttpSession created [ntozzm]

Can it be this the problem.We have also looked about this problem but it seems to be something else.

Daniel Ebers

Hi Reto,

a reboot should not kill anything but on the other side there is nothing unusual from the logs you posted.
Also a healthy system shows those lines during authentication.

There are two entries in knowledge base but but of them report that those errors would write to atlassian-jira.log - you mentioned atlassian-jira-security.log which is also an important one but probably will never show in-depth trouble with the authentication mechanism itself (rather information to the actually logins/failed logins - rather security relevant information).

So in first steps I'd like you to review atlassian-jira.log for any potential errors.

• Active Directory users fail to logon intermittently
  https://confluence.atlassian.com/jirakb/active-directory-users-fail-to-logon-intermittently-945118456.html
• Users not able to log into JIRA using LDAP Connector AD
  https://confluence.atlassian.com/jirakb/users-not-able-to-log-into-jira-using-ldap-connector-ad-297666580.html

Something theoretical before stopping here: could it be due to a missing SSL certificate agains Active Directory which were present until reboot? This, unfortunately is only a wild guess without knowing the server.

Please let us know what you found out.

Regards,
Daniel