Search Engine: Elastic

Article ID: 130419, created on Mar 13, 2017, last review on Mar 13, 2017

  • Applies to:
  • Operations Automation 7.0


OSA has been upgraded from 6.0 to 7.0.

During the upgrade, a brand was migrated to a new host, dedicated for hosting brands, per the upgrade workflow procedures.

The brand hosted a protected page, served by Apache basic authentication module, e.g. a secured proxy-store web page

Former configuration:

<Directory "/usr/local/pem/vhosts/100001/webspace/httpsdocs/store">
        Require valid-user
        AuthType basic
        AuthUserFile /usr/local/pem/vhosts/100001/webspace/pd/1
        AuthName "Please provide user password"

New configuration in /etc/httpd/conf.d/ does not include the same settings.


All customized Apache configuration for branded sites should be backed up and re-applied after the upgrade to 7.0, as the approach to hosting brands has been completely re-worked.


In order to restore the basic authentication for a particular page, e.g., follow the steps below:

  • create store directory in the website root:

    # mkdir /var/www/brands/
  • copy the file storing user passwords for Apache authentication from the original node, e.g. /usr/local/pem/vhosts/100001/webspace/pd/1/.htpasswd, and save it as /var/www/brands/

  • create /var/www/brands/ file with the following content:

    require valid-user
    AuthType basic
    AuthUserFile /var/www/brands/
    AuthName "Please provide user password"

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF