AEM - Restricting CRXDE Access for few users | AEM Community Seeding

[#1]

AEM - Restricting CRXDE Access for few users by Arun Patidar

Abstract

In AEM, CRXDE access can be disabled by

1. Disabling the required bundles
Adobe CRXDE Support (com.adobe.granite.crxde-support)
Adobe Granite CRX Explorer (com.adobe.granite.crx-explorer)
Adobe Granite CRXDE Lite (com.adobe.granite.crxde-lite)
2. From dispatcher https://helpx.adobe.com/experience-manager/kb/LimitAccessCRXandCRXDE.html

What if CRXDX needs to be disabled/restricted for a few users/groups.
One of the solutions could be to check the user when the user attempts to access CRXDE and block the access or re-route.

Step to Implement the above approach :
1. Create a Sling Filter to check the CRXDE access request.
2. Create an OSGi configuration and service to maintain restriction data(Users, groups, excluded user)
3. Create a clientlibs to re-route the user to another page while accessing CRXDE.

In the Sling Filter get the current user and check against service configuration and if found then replace/redirect one of the existing js to our custom clientlibs js.
Custom clientlibs will then take care of blocking CRXDE.

Read Full Blog

AEM - Restricting CRXDE Access for few users

Q&A

Please use this thread to ask the related questions.

[#2]

Link given is redirecting to incorrect page.

[#3]

Thank you for notifying me about this. I have made the edits.

-Kautuk

[#4]

Hi we are using AEM 6.5, and I have tried this method in my local, but it is not working. I am getting:

Service unaviable: Can neither derive user name nor principal names for bundle com.example.core [608] and sub service readService

I have followed this link and tried to create a mapping to configure a bundle-to-user mapping as well, but it is not working either.

Can anyone help me on it?

Thanks