CUG login not working on publish server after restart | Community
Skip to main content
January 14, 2019
Solved

CUG login not working on publish server after restart

  • January 14, 2019
  • 5 replies
  • 1903 views
We have configured CUG for certain pages in our site and configured a login page to which all the unauthenticated requests should be redirected to. After restarting our AEM 6.3  SP2 publish server, the login for CUG protected sites is no longer working.When we hit the secure page, the publish server returns a 404.Any ideas what could be the problem?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by akhilat9657589

Please check if the user cug-service is having access to /content node.

Thanks,

Akhila

5 replies

Gaurav-Behl
Level 10
January 14, 2019

Could you share the relevant logs?

Did you check all required configurations and ACLs are intact?

Did this behavior happen as a result of any update/patch?

smacdonald2008
Level 10
January 14, 2019

What are the log messages for this? Seem very wierd that it works and stops working when you restart the service.

Also - make sure that the CUG is properly setup and all of the files are located on the server - such as the login page.

kautuk_sahni
Community Manager
Community Manager
January 15, 2019

Please check if the redirected page exists. Is there dispatcher in picture as well?

Reference community article: http://www.aemcq5tutorials.com/tutorials/implement-cug-aem/

Kautuk Sahni
smacdonald2008
Level 10
January 15, 2019

Kautuk brings up a good point - is Dispatcher somehow playing a role in this behavior.

akhilat9657589Accepted solution
Level 2
January 18, 2019

Please check if the user cug-service is having access to /content node.

Thanks,

Akhila