Aem sites locked for anonymous users

[demd43642519]

Hi guys!

Recently under unknown modification the publisher instance can't be accessed by anonymous users. Only logged user can access the publisher instance.

How do I change that?

I'm using AEM 6.2 and I've already check user admin for anonymous user permissions.

Any suggestions?

Thanks!

-------------------------

I also get this when I start the instance:

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

20.07.2018 10:44:38.244 *INFO* [qtp431714949-101] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *INFO* [qtp431714949-102] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

[edubey]

Can you check this particular config once, It should be checked

[demd43642519]

Yep, that's checked.

[smacdonald2008]

Sounds like that instance is configured as an author instance. Check to make sure its properly configured for Pub - Run Modes

[demd43642519]

Hmm, I don't think so because If it would be an author instance it should redirect me tot the AEM login page.

But when I access any page I get this 403 error.

[Kunwar]

302 status code would suggest an issue on the apache level or resource mapping configuration. Can you bypass the webserver and directly try hitting the author/publish instance

[demd43642519]

Hmm, I don't think I understand.

My experience is not so vast so I don't know what are you talking about by "bypass the webserver and directly try hitting the author/publish instance.

Can you please detail?
Thanks

[Kunwar]

Try hitting the instance with direct host port (http://HOST:PORT/<CONTENT_PATH>.html) and see if anonymous users can access the page or not

[demd43642519]

No, I can't.  I get that 302 status code.

I'm only allowed to access it after i get login in into crx/de. when i'm logged as an administrator. And I don't understand which may be the cause.

[smacdonald2008]

Has this been happening since the Server was installed or was fine then started happening.

[demd43642519]

It was fine before. but under unknown modification this started to happen so I'm willing to find which may be the cause of this because I have no idea where should I be looking into.

Do you think it has something to do with the etc/maps ?

[smacdonald2008]

Click Allow Anonymous User and re-boot the server - see if that helps.

[demd43642519]

Allow Anonymous User is checked and I reboot the server. Didn't help.

Also I get this while the instance starts:

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.150 *ERROR* [qtp431714949-100] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

20.07.2018 10:44:38.244 *INFO* [qtp431714949-101] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *INFO* [qtp431714949-102] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Abort login due to apparent misconfiguration.

20.07.2018 10:44:38.337 *ERROR* [qtp431714949-102] com.day.cq.auth.impl.LoginSelectorHandler requestCredentials: Possible reasons: login page not existing or not accessible

[VeenaVikraman]

May be you can raise a day care ticket (Adobe Support ticket) . I am not sure if your system is corrupted for any reason ?

[TomaszSz2]

I had the same issue and in my case the reason was incorrect sling mapping configuration. Try to remove sling mappings you have in /etc/map/... and check if the author instance will work fine. If it will work fine after removing the sling mapping config then you will have to find out what is wrong with it.