CUG login not working on publish server after restart | Community
Skip to main content
New Participant
Jan 14, 2019 5:08 AM UTC
Solved

CUG login not working on publish server after restart

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.
akhilat9657589Accepted solution
Level 2
Jan 18, 2019 8:50 AM UTC

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

Thanks,

Akhila

5 replies

akhilat9657589Accepted solution
Level 2
Jan 18, 2019 8:50 AM UTC

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

Thanks,

Akhila

Translate
smacdonald2008
Level 10
Jan 15, 2019 3:48 PM UTC

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

Translate
kautuk_sahni
Employee
Jan 15, 2019 1:00 PM UTC

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/

Translate
Kautuk Sahni
smacdonald2008
Level 10
Jan 14, 2019 6:34 PM UTC

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.

Translate
Gaurav-Behl
Level 10
Jan 14, 2019 5:34 PM UTC

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?

Translate