How to make CQ5 working with enabled basic http authentication dispatcher | Community
Skip to main content
tnguyenv
tnguyenv
New Participant
October 16, 2015
Solved

How to make CQ5 working with enabled basic http authentication dispatcher

  • October 16, 2015
  • 3 replies
  • 5923 views

Hi everyone,

I have a problem about the configuration that to make my AEM public instance (version 5.6.1) working properly in enabled basic http authentication (user/password) dispatcher environment. I got other authentication request from Sling after passed http authentication. I was not aware of this and fail to log in with any my AEM account.

Please help advice me.

Thanks

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 joerghoh

Let me try to rephrase your problem:

  • You need to support basic authentication on your webserver/dispatcher.
  • But when you have authenticated yourself and you send an request with basic header to the AEM publish instance, the publish instance promptes you for your credentials (basic auth).

Is that correct?

If that's the case, you are affected by the preemptive authentication approach of Sling. You have 2 choices:

HTH,

Jörg

3 replies

2
25793466
New Participant
April 12, 2018

I want to disable basic authentication and ran across this thread.  I know this will break replication, but I'm just curious on how to do it.  It appears that I can set HTTP Basic Authentication on http://localhost:4502/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator to Disabled, but that doesn't seem to work on several AEM 6.2 instances I have tested on.  Replication is still working and I can pass the basic authentication headers to the admin UI and it logs me in.

joerghoh
joerghohAccepted solution
Employee
October 16, 2015

Let me try to rephrase your problem:

  • You need to support basic authentication on your webserver/dispatcher.
  • But when you have authenticated yourself and you send an request with basic header to the AEM publish instance, the publish instance promptes you for your credentials (basic auth).

Is that correct?

If that's the case, you are affected by the preemptive authentication approach of Sling. You have 2 choices:

HTH,

Jörg

    tnguyenv
    tnguyenvAuthor
    New Participant
    October 16, 2015

    Jörg Hoh wrote...

    Let me try to rephrase your problem:

    • You need to support basic authentication on your webserver/dispatcher.
    • But when you have authenticated yourself and you send an request with basic header to the AEM publish instance, the publish instance promptes you for your credentials (basic auth).

    Is that correct?

    If that's the case, you are affected by the preemptive authentication approach of Sling. You have 2 choices:

    HTH,

    Jörg

     

    Thanks Jorg. This is my case. Could you can give me the instructions more details or reference articles regarding this problem?

    Terms & ConditionsAccessibility statement

    Loading footer...