Loading...

Details

Type: Bug
Resolution: Unresolved
Priority: Low
Fix Version/s: None
Affects Version/s: 7.1.2, 7.2.0-OD-03
Component/s: Project Administration - Permissions
Labels:
- affects-cloud
- affects-server

Introduced in Version:
7.01
Support reference count:
9
Symptom Severity:
Severity 3 - Minor
UIS:
0
Bug Fix Policy:
View Atlassian Server bug fix policy

Description

NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

Summary

If a user is created and added to a permission scheme, and then the user is later deleted (not deactivated), if the user still remains in the permission scheme before they are deleted, the permission scheme will show as a blank screen, the browser will throw a 500 error in the browser console, and the NPE will appear in the log file (shown below).

Steps to Reproduce

Create a user in User Management.
Navigate to Issues > Permission Schemes.
Add the user you created to any permission in a permission scheme of your choice.
After the permission has been granted, delete that new user in User Management.
Navigate to Issues > Permission Schemes and select the permission scheme you used in step 3. The scheme will not load.

Expected Results

The permission scheme should load and you should be able to edit the permissions.

Actual Results

The below exception is thrown in the JIRA log file, and the permission scheme will not load in the browser:

2016-03-04 15:02:33.588560500 2016-03-04 15:02:33,584 http-nio-2998-exec-555 ERROR sysadmin 902x172511x1 jvz64d 4.15.43.214,10.84.193.150,127.0.0.1 /rest/internal/2/managedpermissionscheme/10600 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null
2016-03-04 15:02:33.588563500 java.lang.NullPointerException
2016-03-04 15:02:33.588563500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService.updateSchemeToReturnUsername(DefaultPermissionSchemeService.java:436)
2016-03-04 15:02:33.588564500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService.access$2200(DefaultPermissionSchemeService.java:58)
2016-03-04 15:02:33.588611500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService$13.apply(DefaultPermissionSchemeService.java:331)
2016-03-04 15:02:33.588612500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService$13.apply(DefaultPermissionSchemeService.java:327)
2016-03-04 15:02:33.588613500 	at com.atlassian.fugue.Option$Some.fold(Option.java:421)
2016-03-04 15:02:33.588613500 	at com.atlassian.fugue.Option.flatMap(Option.java:287)
2016-03-04 15:02:33.588621500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService.getScheme(DefaultPermissionSchemeService.java:327)
2016-03-04 15:02:33.588622500 	at com.atlassian.jira.permission.DefaultPermissionSchemeService.getPermissionScheme(DefaultPermissionSchemeService.java:105)
2016-03-04 15:02:33.588630500 	at com.atlassian.jira.permission.management.ManagedPermissionSchemeHelperImpl.getManagedPermissionScheme(ManagedPermissionSchemeHelperImpl.java:92)
2016-03-04 15:02:33.588631500 	... 2 filtered
2016-03-04 15:02:33.588631500 	at java.lang.reflect.Method.invoke(Method.java:497)
2016-03-04 15:02:33.588632500 	at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
2016-03-04 15:02:33.588638500 	at com.sun.proxy.$Proxy550.getManagedPermissionScheme(Unknown Source)
2016-03-04 15:02:33.588639500 	... 2 filtered

Workaround

The value (user or group) needs to be removed from the scheme in the database. Use the following steps:

Find the permission scheme ID (it will either be in the URL, or in the stack trace. In this case, you can see in the log file that it is '10600'. This value will be used in this example;
Access JIRA's database;

Run the below query to find invalid user entries on the permission scheme;

SELECT * FROM schemepermissions WHERE perm_type = 'user' AND perm_parameter NOT IN (
	SELECT lower_user_name FROM cwd_user WHERE directory_id IN (
		SELECT id FROM cwd_directory));

Delete those entries directly through the database;
Restart JIRA;

This will remove that user from all permission schemes they are associated with.

Attachments

Issue Links

duplicates

JRASERVER-59781 Permission Scheme cannot be edited when it includes a single user

Closed

JRASERVER-59683 Permission schemes with non-existent users that have been explicitly granted a permission cannot be edited

Gathering Impact

relates to

JRACLOUD-60080 Permission Scheme 500 Error and Nullpointerexception

Closed

mentioned in: Page Loading...

Permission Scheme 500 Error and Nullpointerexception