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

Manage Jira using AD account and not local account "jira"

Edited

We have recently migrated Jira to new environment and the way the users accounts are managed is different than current one.

We used to have a local account "jira" under /etc/passwd or shadow and then set the permissions to the install orhome or sharedhome directories with jira:jira that were created locally that has got same UID across the 4 node cluster

I new environment, the user "jira" is setup in AD and the UID is different across different instances and the shared-home directory would change its ownership to the username that the ID is pointed to (each instance has different users for same id).

What is the best way we can bring the cluster up without any variance in UID/user account?

 

1 answer

i am facing the same issue migrating to new environment ?

any suggestions fm atlassian that helped ?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.13.7
TAGS
AUG Leaders

Atlassian Community Events