To Verify That the Administrator Session Fails Over

Before You Begin

Both OpenSSO Enterprise 1 and OpenSSO Enterprise 2 should be up and running before you begin this verification procedure.

1. As a root user, log in to the osso–2 host machine.

2. Change to the bin directory.

   # cd /export/osso80adm/domains/ossodomain/bin

3. Stop OpenSSO Enterprise 2.

   # ./stopserv

4. Access https://lb-2.example.com:1081/opensso/console from a web browser.

   1. Log in to the OpenSSO Enterprise console as the administrator.

      Username

      amadmin

      Password

      ossoadmin

   2. Click the Sessions tab.

   3. In the View field, select osso-1.example.com:1081 from the drop down list.

      Verify that only amadmin exists in the Sessions table.

   4. In the View field, select osso-2.example.com:1081 from the drop down list.

      You will see an error message indicating the server is down.

   5. Leave this browser window 1 open.

5. Start OpenSSO Enterprise 2.

   # ./startserv admin username:domain2adm admin password:domain2pwd master password:domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log

6. As a root user, log in to the osso-1 host machine.

7. Change to the bin directory.

   # cd /export/osso80adm/domains/ossodomain/bin

8. Stop OpenSSO Enterprise 1.

   # ./stopserv

9. Going back to the OpenSSO Enterprise console in browser window 1, under the Sessions tab, select osso-1.example.com:1081 from the View drop down list.

   You will see an error message indicating the server is down.

10. Now select osso-2.example.com:1081 from the View drop down list.

    Verify that only amadmin exists in the Sessions table. This indicates that although OpenSSO Enterprise 1 was stopped, the OpenSSO Enterprise Load Balancer 2 directed the request to OpenSSO Enterprise 2 and a session for amadmin was successfully created by OpenSSO Enterprise 2. If session failover was not enabled, it would have resulted in a login page.