I have been using the same deployment with evaluation keys and now migrated to my production license key, which is only a Starter License. But due to misuse of the system, I am stuck without the ability to perform users mapping.
My problem start with this scenario:
I have problems with upper case usernames and lower case usernames in Fisheye/Crucible integrating with our LDAP. Our repository had all usernames in lower case. LDAP has some upper case usernames. Since Crucible is configured to automatically add users from our LDAP server, i find myself only be able to login with my upper case username in Fisheye/Crucible. Then i switched Crucible to force user lower case usernames only. And that did not solve my login problems so i started to delete users and re-syncing them again from LDAP. Because of this, i am left without any committers to map to users who are licensed to login.
Hi KY Lee,
To start with, this sounds a little complex so feel free to raise an issue at support.atlassian.com so you can work through it with our support team.
I'm not clear what state your system is in now. Are users able to log in? Are you able to manually map committers to users through the admin interface ("User Settings" / "User mappings" in the admin left hand categories), or are users able to map committers for themselves (User menu / "Settings" / "Author Mapping")?
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events