-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QA] 0.5.2 Testplan #206
Comments
Issues to re-review
Changelog testing
|
@jnweiger I was going to try some scenario with multiple groups related to #202 because, from seeing the code, I think that there might be a problem. I have groups called
then I expect that the admin will be able to impersonate But when I login as admin and go to the Users page, I don't see the "impersonate icon" for any of the users. And I don't see the Admin Settings, User Authentication setting any more. The app settings are:
I suspect that something in core does not even think that the app is enabled, because "enabled" is not set to "yes".
|
Now I understand that both the impersonator (usually an admin, or a subadmin of a group) has to be in one of the allowed groups, and also the target user (impersonatee - is that a word) also has to be in one of the allowed groups. If I do:
then I get closer. The admin user (who is in the admin group) can now go to the Users page and see the Impersonate icon for other users. But it will not let me impersonate any user. Even though user The problem is that the code, accidentally, only allows a user to be impersonated if they are a member of every group in the list of allowed groups. I adjusted the logic of that in PR #208 and now admin can impersonate user |
@jnweiger there were a lot of changes merged to the release branch yesterday. I think the code should be good now. Needs another RC built, and test with that. |
@jnweiger I guess that this issue can be closed? |
Setup
Impersonate Test Plan
The text was updated successfully, but these errors were encountered: