Expected bahaviour of standby instance about experience-manager-65.en HOT 5 CLOSED

Thank you for creating this issue, @BharathValse . However I am unclear what it is that you would like us to add. What exactly is the expected behavior of the standby instance in the situation that you describe?

from experience-manager-65.en.

Thanks for looking into this @bohnertchris.

When the standby instance is setup or derived from Primary node, admins try to access the welcome screen of AEM and other consoles which results in an Authentication service missing error like [0] on the browser. It is expected that the standby instance doesn't open up these general AEM consoles and only opens up the CRXDE lite and OSGI web console for admin related activities.

Since this behavior is not documented, it leads to confusion that the standby instance is not set up right and corrupted.

[0]
HTTP ERROR 503
Problem accessing /aem/start.html. Reason:

AuthenticationSupport service missing. Cannot authenticate request.

from experience-manager-65.en.

Thank you for the further information, @BharathValse . It makes the problem clearer and we will have a look.

from experience-manager-65.en.

CQDOC-15720

from experience-manager-65.en.

Thanks for highlighting this - a note has been added.
Closing this issue.

from experience-manager-65.en.