Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.3.X, Master
-
7.3.x, 7.2.x
-
Committed
-
3
Description
With the inclusion of LPS-134096, a small condition was added to return early if all default roles were already associated with the user. This can cause problems however, because it was determined in this comment the "User" role should always be assigned to the user, even when explicitly removed from the Default User Associations entry has been removed.
This ticket describes the opposite behavior of LPS-149351, which was closed as "Won't Fix".
Steps to reproduce:
- Go to Instance Settings > Users > Default User Associations.
- Remove the "user" role. Save.
- Create a new user.
- Look at the newly created user's "user_roles" entrie(s) in the DB (the "User" role will not appear in the Roles Admin portlet, so using the DB is the only way to verify it's been assigned or not).
Expected Results:
New user should still have the "User" role.
Actual Results:
New user does not have the "User" role.