Deployment Example 1: Access Manager 7.0 Load Balancing, Distributed Authentication UI, and Session Failover

ProcedureTo Reconfigure Access Manager 1 to Run as a Non-Root User

  1. As a root user, log into host AccessManager-1.

  2. Stop Access Manager 1.


    # cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/
    # ./stop
  3. Stop the Web Server administration server.


    # cd /opt/SUNWwbsvr/https-admserv/ 
    # ./stop 
  4. Change the “runs as” user ID from root to nobody.


    # cd /opt/SUNWwbsvr/ 
    # chown -R nobody:nobody https-AccessManager-1.example.com/* httpacl alias \
    /var/opt/SUNWam /etc/opt/SUNWam 
    # rm  -rf /tmp/https-* 
  5. Edit the magnus.conf file.

    It is a good practice to make a backup of this or any other configuration file before making changes to the file.


    # vi https-AccessManager-1.example.com/config/magnus.conf

    Change the User property value from root to nobody.

  6. Verify that Access Manager successfully runs as a non-root user.

    1. Log in as a root user to the Access Manager host.

    2. Start the Access Manager server.


      # cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/ 
      # ./start
    3. Confirm that the Web Server start process actually runs as nobody.


      # ps -ef | grep SUNWwbsvr
    4. Start a new browser and go to the Access Manager URL.

      Example: http://AccessManager-1.example.com:1080/amserver/console

      Close the browser if successful.

    5. Log in to the Access Manager console using the following information:

      Username

      amadmin

      Password

      4m4dmin1

      If you can log in successfully, close the browser.