Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Content is not visible on publish instance for anonymous users

Avatar

Level 4

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?

1 Accepted Solution

Avatar

Correct answer by
Level 10

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

View solution in original post

4 Replies

Avatar

Correct answer by
Level 10

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

Avatar

Level 4

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?

Avatar

Level 10

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