How is it possible to disable Site Admin actions for particular groups, e.g. Activate?
Is it possible to disable admin account in CQ 5.5? Please if any one having any idea about this.
Solved! Go to Solution.
Views
Replies
Total Likes
Why not simply limit access to the admin account, change the password and entrust it to a select few who will not use it to carry out admin tasks?
Then provide administrator privileges and felix console access to users that need to carry out admin duties. This is a simpler way to control access without disabling the default system administrator account.
Regards,
Opkar
Views
Replies
Total Likes
Hi,
why do you want to disable the admin account?
Have you set up users with administration privileges and access to the felix console already?
Regards,
Opkar
Views
Replies
Total Likes
Hi
Please share the use case of disabling the admin account.
If you would like to deny access to site admin actions for particular group, then please have a look at the following :-
How is it possible to disable Site Admin actions for particular groups, e.g. Activate?
Following the concept 'Everything is content', Site Admin actions as such are also pure nodes in the repository which are thus subject of access control.
In order to disable and completely hide a certain action in the Site Admin console for a particular group, a corresponding group ACL has to be defined that denies read access to this action.
Following example will deal with the Activate action.
In order to set the actual ACL on above action node, the CRX Content Explorer has to be used. Following are the steps how to disable the Activate action for a group:
At this point, members of the above specified group won't have access to the Activate action anymore.
Based on the above given instructions, basically all other actions available in the Site Admin can be equally controlled via permissions. Following is a list of paths under which actions reside for different consoles:
Console | Path |
Site Admin | /libs/wcm/core/content/siteadmin/actions |
DAM Admin | /libs/wcm/core/content/damadmin/actions |
Tools | /libs/wcm/core/content/misc/actions |
Security Admin | /libs/cq/security/content/admin/authlist/actions |
Link:- https://helpx.adobe.com/experience-manager/kb/how-to-deny-access-to-site-admin-actions.html
Thanks and Regards
Kautuk Sahni
Views
Replies
Total Likes
Coming to auditing point, we are getting admin related information. So that planning to disable admin and access with other guy who hav admin rights.
Views
Replies
Total Likes
Why not simply limit access to the admin account, change the password and entrust it to a select few who will not use it to carry out admin tasks?
Then provide administrator privileges and felix console access to users that need to carry out admin duties. This is a simpler way to control access without disabling the default system administrator account.
Regards,
Opkar
Views
Replies
Total Likes
Opkar's suggestion is best practice with AEM.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies