Hello,
I've connected JIRA 5.0.1 to our MS Active Directory by creating a new user directory in JIRA. All my users from the AD are well added to this new JIRA directory.
However groups linked to those imported users come from the AD and are not the groups previously defined in JIRA (such jira-users, jira-developers, …).
Is there a way to link existing group from JIRA and to avoid importing the groups from the Active Directory when I'm importing users from AD?
Thank you.
Hi there,
In order to use JIRA groups for your LDAP users you will need to configure your LDAP directory to use "Read Only with Local Group" permission setting.
In order to avoid your directory to synchronize the LDAP groups into your JIRA, you will need to create a search filter that can't retrieve any groups. For example using "DummyValue" such as
(objectCategory=DummyValue)
In order to configure a default group(s) for all of your LDAP users, you could use "Adding Users to Groups Automatically". This feature will allow your LDAP users to be added into the configured local group(s) automatically during their first log-in.
Hope it helps.
Cheers,
Septa Cahyadiputra
Hi Septa,
Thank you very much for your answer, it helps in this way that my imported users are not linked to AD groups.
However is there a way to assign default JIRA groups when importing those users such it works when I create a user manually in JIRA? Do we exclusively need working with Crowd for that?
Thank you!
François.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it is possible. Just update my first answer, please refer to my edited answer.
Cheers,
Septa Cahyadiputra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pleasure is all mine :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Septa,
absolutely perfect! Thank you very much for your great help.
François.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
30 karma pts should be granted to Septa's answer.. That is correct..
What more are you looking for in this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ouch on that down-vote?
Not sure what that was for - Harsh! - indeed Septa's answer was correct, after validating in our engineering as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Depending on how big your AD is, if you have nested groups, and also if you want similar group management in more than one Atlassian app, you might want to consider using Crowd for additional controls and SSO between the apps ..
Here's for filtering in Crowd..
https://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.