Add all users in X groups to jira-users

Stian Bentsen Sveen

Hi,

We've set up a pretty rigid project access setup using security groups in AD.

All projects have a dedicated security group, "JIRA-Project-xxxx" that gives access to a specific project, and we also have some group that will have access to multiple projects (like f.ex "JIRA-Group-IT"), but we also want all these users to automatically become a member of jira-users so I can handle application access by giving jira-users "JIRA Software" access and not have to give that to every single group I make. I also want to use jira-users for our PMO since they want "any logged in user" to have access to their PMO project that contains project statuses etc for our business projects. Problem is, I cant delegate access to a project to "any logged in user" like I can with a filter / dashboard.

Also I cant auto add them to this group via user directories as they sync a whole bunch of users who shouldnt have JIRA access (only synced to become a customer in the Service Desk).

What I would've liked is to use f.ex ScriptRunner to create a scheduled job running so so often to get members from groups beginning with "JIRA-xxx" and incrementally add them to jira-users automatically.

Is this possible or is there another way I can do this?

I cant be adding every new JIRA Software user manually to this group in addition to the security group for the project.

Any ideas are welcome.

Thanks!

Br,

Stian

 

Andy Heinzer

Hi,

The best way to approach this could require adjustments to both Jira and the structure of your AD/LDAP instance.   The examples in How to write LDAP filters can be useful here.  The ideal solution would be to use the matching components of distinguished names.  However our own KB notes that Active Directory specifically does not support this:

As Microsoft Active Directory does not implement extensible matching, the following examples won't work with it.

In your case, the ideal situation would be to have a parent group to all of the 'JIRA-Project-xxx' groups that exist.  In this way, you could then look at the nested group membership of this parent group and in turn assign application access on that one group.   

However from what you have stated so far, I can't tell if your Active Directory structure is setup this way or not.  This parent group should also be separated from any service desk only users to avoid granting them application access when those unlicensed users are not expected to have this.

One way you might look into here would be to separate your user directories in Jira to create a completely separate user directory just for syncing in the Service Desk customers that you don't want to have other application access.  This would at least allow you to create more specific LDAP filters in the user directory settings in Jira.

My thought process on this would then potentially allow you to more closely refine the LDAP filters in your other user directory that you want to use to assign jira-user membership to more easily.   

In addition to trying this approach, it's possible you might be able to use the Read only with local groups option here to help solve this.  This option let's you grant an internal group membership to all the users of a specific user directory.  If you can refine this directory down to be all the users you want in jira-users and exclude all the service desk users in the other user directory, this could be one way you could achieve this kind of group membership based on your security groups without having to completely re-arrange the LDAP/AD structure.