Having some trouble assigning security groups on a master UX I call Layout. there are 8 embedded components on the UX within panel cards. These panel cards are split in half, and are accessed with 2 button list controls: LEFTMENU AND RIGHTMENU. These are based on 2 list controls with 4 actions each. The Left menu needs to be accessed by one security group, and the right by another, plus a administrator who has access to both. So I set permissions for 4 of the embedded components to leftgroup and administrator, and 4 to rightgroup and administrator. I also set the security groups at the control level for the controls LEFTMENU, AND RIGHTMENU the same way.
However this doesn't work. What happens is the layout component renders, but then in a few seconds it kicks me to the insufficient permissions redirect page.
So my conclusion is that security is rejecting the user because the alternate permission-ed embedded components although not visible are loading and triggering the redirect.
So my question is not for this specific setup but generally how do you assign security groups to embedded components, in a single UX with divided permissions? If I assign a common group to everyone say group bothmenus, and then go down to control level security and assign groups to the list control menu buttons as previously described this seems to work, but is this the best practice?
It is convenient, and a lot less work to use a single Layout UX component. Rather than a different layout component for each group so it would be helpful to understand the best secure way to do this. Am I diagnosing the problem correctly? My conclusion is control level security shows/hides a control depending upon group assignment. Component level security redirects the user to the insufficient privileges page xxxx for a user not assigned to the required group.
However this doesn't work. What happens is the layout component renders, but then in a few seconds it kicks me to the insufficient permissions redirect page.
So my conclusion is that security is rejecting the user because the alternate permission-ed embedded components although not visible are loading and triggering the redirect.
So my question is not for this specific setup but generally how do you assign security groups to embedded components, in a single UX with divided permissions? If I assign a common group to everyone say group bothmenus, and then go down to control level security and assign groups to the list control menu buttons as previously described this seems to work, but is this the best practice?
It is convenient, and a lot less work to use a single Layout UX component. Rather than a different layout component for each group so it would be helpful to understand the best secure way to do this. Am I diagnosing the problem correctly? My conclusion is control level security shows/hides a control depending upon group assignment. Component level security redirects the user to the insufficient privileges page xxxx for a user not assigned to the required group.
Comment