Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error when adding an AD user to a group

Vasileios Giannakopoulos May 31, 2018

Hello,

When i am trying to add an AD user to a group, i am getting the error below. 

Any ideas what it is or how to fix? When i try to add a local jira user it works fine and the groups exist. The sync between AD and Jira works fine.

Thanks!

Technical details

Log's referral number: 6df5c0d8-8eb1-40f8-bb0c-a3b923f01c3a

Cause

Referer URL: https://issues.savagi.eu/secure/admin/user/BulkEditUserGroups!default.jspa?atl_token=BBIH-2B6M-X92B-L2R1%7C418bc51715fce677c44352dac0268a04904d450f%7Clin&selectedGroupsStr=jira-servicedesk-users

com.atlassian.crowd.exception.runtime.GroupNotFoundException: Group <jira-servicedesk-users> does not exist
com.atlassian.crowd.exception.runtime.GroupNotFoundException: Group <jira-servicedesk-users> does not exist
	at com.atlassian.crowd.embedded.core.CrowdServiceImpl.addUserToGroup(CrowdServiceImpl.java:776) [embedded-crowd-core-2.10.2-rc04.jar:?]
	at com.atlassian.jira.user.util.UserUtilImpl.doAddUserToGroup(UserUtilImpl.java:353) [classes/:?]
	at com.atlassian.jira.user.util.UserUtilImpl.addUserToGroup(UserUtilImpl.java:335) [classes/:?]
	at com.atlassian.jira.bc.group.DefaultGroupService.addUsersToGroups(DefaultGroupService.java:415) [classes/:?]
	at com.atlassian.jira.web.action.admin.user.BulkEditUserGroups.doExecute(BulkEditUserGroups.java:119) [classes/:?]
	at webwork.action.ActionSupport.execute(ActionSupport.java:165) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-7.10.0.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:138) [classes/:?]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) [servlet-api.jar:?]

message was longer but i had to cut it short

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 31, 2018

When using an LDAP/AD directory with Jira, you can't add users from that user directory into groups that exist in other user directories.  The exception to this is if you are using the option called 'Read-only with local groups' and then it only allows you to place LDAP/AD users into groups that exist in the local internal directory for Jira.

Tell us about your specific user directory setting in Jira.  Is this Read only, read only with local groups, or read/write?

I suspect you are seeing this error because your AD does not have a group with this name, OR Jira's group filter is not configured to sync this group on that user directory.

Check those settings first and let us know.   If you have a directory with this name and still see this error, please run these two SQL queries on your Jira database and let us know the results:

select * from cwd_group where lower_group_name='jira-servicedesk-users';

and

select * from cwd_directory;
Vasileios Giannakopoulos May 31, 2018

Hi Andrew,

I am surprised to hear that you can't add users from that user directory into groups that exist in other user directories. 

But it is something you said that gave me the solution. I had the AD as read/write. I changed that to read only with local groups and the issue was resolved.

Thanks a lot for your help!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events