Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

How to give any user the access of http://localhost:4503/system/console/configMgr .

Avatar

Level 7

Hi 

I ama able to access http://localhost:4503/system/console/configMgr using Admin credentials, but I am trying with any other user then I am not able to access if.

 

akshaybhujbale_0-1666370754446.png

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @akshaybhujbale 

 

Follow below steps it works

  1. Create a group using user admin console(IP:PORT/useradmin)
  2. Add this group in another group or user that needs console access
  3. Go to configuration manager(IP:Port/system/console/configMgr)
  4.  Search & edit “Apache Sling Web Console Security Provider”
  5. Add the group (created in step 1) to Group Names field in Apache Sling Web console Security Provider
  6. Save it and you are all set.

View solution in original post

3 Replies

Avatar

Community Advisor

You can add users and groups to the following config that needs web console access

 

http://localhost:4502/system/console/configMgr/org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider

Avatar

Correct answer by
Community Advisor

Hi @akshaybhujbale 

 

Follow below steps it works

  1. Create a group using user admin console(IP:PORT/useradmin)
  2. Add this group in another group or user that needs console access
  3. Go to configuration manager(IP:Port/system/console/configMgr)
  4.  Search & edit “Apache Sling Web Console Security Provider”
  5. Add the group (created in step 1) to Group Names field in Apache Sling Web console Security Provider
  6. Save it and you are all set.

Avatar

Employee Advisor

Do you really want to give someone the chance to re-configure your AEM instance? Anyway, I would never change the OSGI settings on a running Stage/PROD environment via the Webconsole. Instead I would introduce all changes in a controlled way via a deployment.