Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

CUG login not working on publish server after restart

Avatar

Level 1
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?
1 Accepted Solution

Avatar

Correct answer by
Level 3

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

Thanks,

Akhila

View solution in original post

5 Replies

Avatar

Level 10

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?

Avatar

Level 10

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.

Avatar

Administrator

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

Avatar

Level 10

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

Avatar

Correct answer by
Level 3

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

Thanks,

Akhila