Password protecting staging publisher instance in AEM 6.2 | Community
Skip to main content
A
a_lex_
Level 3
March 22, 2017
Solved

Password protecting staging publisher instance in AEM 6.2

  • March 22, 2017
  • 8 replies
  • 5650 views

Hi,

Looking for a simple and effective way to password protect one of our staging publisher instance websites that mirrors content from a production instance under a subdomain. Can this be done through AEM somehow?

 

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 a_lex_
    Decided to go with the Apache basic authentication approach as it is the easiest for our specific requirements. Thanks everyone for your help!

    8 replies

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    March 22, 2017

    The simplest approach is to enable basic authentication on the webserver sitting in front of your staging publish instances. Implementing it with AEM requires more work (and you would implement a feature specifically for non-PROD environments ...).

    Jörg

      MC_Stuff
      MC_Stuff
      Level 10
      March 22, 2017

      Hi Alex,

         Another option is having Authentication Requirements with value of +/  at http://host:port/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator

      Thanks,

        A
        a_lex_Author
        Level 3
        March 23, 2017

        MC Stuff wrote...

        Hi Alex,

           Another option is having Authentication Requirements with value of +/  at http://host:port/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator

        Thanks,

         

        I like the simplicity of this. When I enable this for a path and attempt to go to that path (locally on the instance - not even through dispatcher), it does not give me the login prompt but instead a 403 error along with:

        "You don't have permission to access /system/sling/form/login on this server."

        How can I enable this for anonymous users to authenticate? 

         

        Thank you very much for your help!

        -Alex

        MC_Stuff
        MC_Stuff
        Level 10
        March 24, 2017

        AlexRizzuto wrote...

        How can I enable this for anonymous users to authenticate? 

         

        Sounds like your installation nosamplecontent. Map default login page Or site level at /system/console/configMgr/com.day.cq.auth.impl.LoginSelectorHandler

        If you don't have custom login page configure to /libs/granite/core/content/login

        D
        dragon2A
        Level 5
        March 29, 2017

        Hi Alex,

        Directly try to hit the/libs/granite/core/content/login.html page you will see the login screen after login again it will re-directs to the geometrics page. You have to enter the Url in the browser after the login it will open a specific page. In 6.2 I tried updating the loginselectorhandler with the AEM login page but it didn't work for me. But we can be able to hit the login Url directly in the browser. 

         

        Thanks

        perfecci0nista
        perfecci0nista
        Level 2
        March 30, 2017

        If you are looking for generalized authentication, then use apache basic authentication. It works seamlessly. 

        <Directory C:/Adobe/Apache2.2/htdocs/mysite.com>
                AuthType Basic
                AuthName "Authenticated"
                AuthUserFile C:/Adobe/Apache2.2/.htpasswd
                Require valid-user
            </Directory>

        A
        a_lex_AuthorAccepted solution
        Level 3
        March 30, 2017
        Decided to go with the Apache basic authentication approach as it is the easiest for our specific requirements. Thanks everyone for your help!
        I
        iainc65537558
        Level 3
        October 4, 2018

        We are looking to do a similar thing - In our httpd.conf we have all the dispatcher stuff and also some basic auth directives.  It is presenting the challenge but this is shown on top of the actual rendered page. How did you set up httpd.conf and where were the relevant directives?

        We have tried with Directory and Location and the same happens.

        One thing that might be slightly different is that we are trying to test this on a part of the website eg for testing we are trying to put basic auth behind the woman's page on we-retail /content/we-retail/us/en/women

        Thanks

        Terms & ConditionsAccessibility statement

        Loading footer...