Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Why do I get access denied to http://localhost:8080/lc/system/console/configMg?

Avatar

Level 2

Last year while troubleshooting another problem, Pulkit help me access http://localhost:8080/lc/system/console/configMg.  If my notes are correct, Pulkit told me to use http://localhost:8080/lc/system/console/bundles, but before I can access this site, I had to logon to another site.  However, I cannot find the address for the other site.

 

Bottom line, I am using AEM Forms 6.5 on JEE, and I need to access  http://localhost:8080/lc/system/console/configMg

What are the step to access the configMg site?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@coldwarsoldier Thanks for getting back!

Yes, at times, we have noticed that you have to log in to the CRX console first before you could use any of the other Felix/AEM consoles.

More context: Ideally, when you try to access any URL, it will redirect to </libs/granite/core/content/login.html>, but the abovementioned problem may arise when you have incorrectly updated the Sling authentication service previously.

Now that you're able to login, you can check whether:

1. "Apace Sling Authentication Service" config under /configMgr has the property Authentication Requirements set with (-/libs/granite/core/content/login)

2. Another property, sling.auth.anonymous.user, under the same config was empty/missing, so ensure that the anonymous access is set correctly or not set at all.

 

Feel free to get back in case of any concerns further, we can connect to discuss the same.

 

View solution in original post

3 Replies

Avatar

Correct answer by
Employee Advisor

@coldwarsoldier Thanks for getting back!

Yes, at times, we have noticed that you have to log in to the CRX console first before you could use any of the other Felix/AEM consoles.

More context: Ideally, when you try to access any URL, it will redirect to </libs/granite/core/content/login.html>, but the abovementioned problem may arise when you have incorrectly updated the Sling authentication service previously.

Now that you're able to login, you can check whether:

1. "Apace Sling Authentication Service" config under /configMgr has the property Authentication Requirements set with (-/libs/granite/core/content/login)

2. Another property, sling.auth.anonymous.user, under the same config was empty/missing, so ensure that the anonymous access is set correctly or not set at all.

 

Feel free to get back in case of any concerns further, we can connect to discuss the same.