Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,488
Community Members
 
Community Events
176
Community Groups

"Log in" Issue when one of directory works incorrectly

Edited

Dear Community,

In our company the following user directories for authentication are used in Jira:

  • domain1.com (Microsoft Active Directory)
  • domain2.com (Microsoft Active Directory)
  • Jira Internal Directory

The domain2.com Domain Controller has frozen with no error this weekend. Then users of all the other directories hadn’t an opportunity to log on to Jira as long as the domain2.com Domain Controller started working correctly. Jira restart couldn’t help to solve the problem. Even Jira Internal users couldn’t log on to Jira. The application was working (the webpage was opened) before the authorization. During an authentication attempt the application has frozen on login and failed with timeout error.

The log-files that indicate error:

2019-11-02 14:19:09,182 http-nio-8083-exec-34 ERROR anonymous 856x1919x40 1m21eq 10.10.10.1,127.0.0.1 /rest/usermanagement/1/authentication [c.a.c.manager.application.ApplicationServiceGeneric] Directory 'Domain2' is not functional during authentication of 'example-user'. Skipped.

 Is that typical for authorization process when problems arise at one of connected directories? Is there a way we can avoid such a situation but to configure access to the user directory through a proxy?

We look forward to your reply.

Many thanks!

0 comments

Comment

Log in or Sign up to comment