Content is not visible on publish instance for anonymous users | Community
Skip to main content
D
demd43642519
Level 4
January 21, 2019
Solved

Content is not visible on publish instance for anonymous users

  • January 21, 2019
  • 4 replies
  • 1809 views

Hi guys,

I have two AEM instances, 1 author and 1 publish.  While on the author instance my menu is visible, on the publish instance is not.

It only became visible once I login as an administrator on the publish.

I am using AEM 6.4 and I've never seen this before.

What could be the issue on this one?

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 Gaurav-Behl

Validate the run mode of publish server - http://localhost:4502/system/console/status-slingsettings

Validate the anonymous user has read access on your content -  http://localhost:4502/useradmin

Validate the Sling Authentication Service configurations in http://localhost:4502/system/console/configMgr  > Apache Sling Authentication Service > Allow anonymous access and authentication requirements fields

4 replies

Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
January 21, 2019

Validate the run mode of publish server - http://localhost:4502/system/console/status-slingsettings

Validate the anonymous user has read access on your content -  http://localhost:4502/useradmin

Validate the Sling Authentication Service configurations in http://localhost:4502/system/console/configMgr  > Apache Sling Authentication Service > Allow anonymous access and authentication requirements fields

smacdonald2008
smacdonald2008
Level 10
January 21, 2019

See this older thread -- Unsecured Page or anonymous page access

D
demd43642519Author
Level 4
January 21, 2019

Hi there,

I've checked everything.
I set read access for anyninmous user.

Run mode is:

 Run Modes = [s7connect, crx3, samplecontent, publish, crx3tar]

Also on Apache Sling Authentication Service i've checkd.

I still have the same behavior. Are there any others services I should config for this?

Gaurav-Behl
Gaurav-Behl
Level 10
January 21, 2019

Did you validate that your application's content is allowed anonymously in publish under Apache Sling Authentication Service > authentication requirements fields ?

E.g. if your menu/content is in /content or whatever path that configuration should be something like

-/<pathname> or -/ for root

if your content pulls /etc/or /content/dam dependencies or csrf token then it should also be allowed as anonymous,

validate the permissions for csrf token.json as well

Terms & ConditionsAccessibility statement

Loading footer...