Details
-
Bug
-
Status: Closed
-
High
-
Resolution: Won't Do
-
3.2.0
-
None
-
None
-
None
-
Flagged
-
Pulsar
-
Platform sprint 126
Description
When a group definition node (hipposys:group) is located under two level groupfolder nodes (hipposys:groupfolder), then the group node doesn't become effective. So, as a result, login failed if a user is included in that specific group.
This works in 10.1.x, but not working in 10.2.0. So, it's a regression.
Test Case
- Create a 10.2.0 project using archetype.
- Build/run CMS.
- Try to login by author/author. You can log in by default.
- Now, create a group folder at /hippo:configuration/hippo:groups/groupfolder1 and move the author group node to /hippo:configuration/hippo:groups/groupfolder1. groupfolder1 is type of hipposys:groupfolder. Save. Try to login by author/author in CMS UI again. You can still log in successfully.
- Now, create another group folder in a deeper level at /hippo:configuration/hippo:groups/groupfolder1/groupfolder2. groupfolder2 is type of hipposys:groupfolder, too. And move author group node into the groupfolder1/groupfolder2 node, resulting in /hippo:configuration/hippo:groups/groupfolder1/groupfolder2/author. Save. Try to login by author/author again in CMS UI. Now, you cannot login.
- The Login UI shows error: "Access to this application is not allowed for this user."
Attachments
Issue Links
- is a result of
-
REPO-672 Session login takes too long and invokes a search
- Closed