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

ProcedureTo Verify that Web Policy Agent 1 Works Properly

  1. Start a new browser and go to the Access Manager URL.

    Example: https://loadbalancer-3.example.com:9443/amserver/console

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

    Username

    amadmin

    Password

    4m4dmin1

  3. Create a referral policy in the top-level realm.

    1. On the Access Control tab, under Realms, click example.com.

    2. Click the Policies tab.

    3. On the Policies tab for example.com-Policies, click New Referral.

    4. In the New Policy page, provide the following information:

      Name:

      Referral URL Policy for users realm.

      Active:

      Mark the Yes checkbox.

    5. On the same page, in the Rules section, click New.

    6. Select a Service Type.

      On the page “Step 1 of 2: Select Service Type for the Rule,” select URL Policy Agent (with resource name)

    7. Click Next.

    8. On the page “Step 2 of 2: New Rule,” provide the following information:

      Name:

      URL Rule for ProtectedResource-1

      Resource Name:

      http://ProtectedResource-1.example.com:1080/*

    9. Click Finish.

    10. On the same page, in the Referrals section, click New.

    11. In the New Referral — Sub Realm page, provide the following information:

      Name:

      Sub-Realm users

      Filter:

      Type an asterisk (*), and then click Search.

      Value:

      In the list, choose users.

    12. Click Finish.

    13. On the New Policy page, click Create.

      In the Policies tab for example.com — Policies, you should see the policy named “Referral URL Policy for users realm.”

  4. Create a policy in the users realm.

    1. Click Realms.

    2. On the Access Control tab, under Realms, click the Realm Name users.

    3. Click the Policies tab.

    4. On the Policies tab for users-Policies, click New Policy.

    5. In the New Policy page, provide the following information:

      Name:

      URL Policy for ProtectedResource-1

      Active:

      Mark the Yes checkbox.

    6. On the same page, in the Rules section, click New.

    7. On the page “Step 1 of 2: Select Service Type for the Rule,” click Next.

      The Service Type “URL Policy Agent (with resource name) is the only choice.

    8. On the page “Step 2 of 2: New Rule,” provide the following information:

      Name:

      URL Rule for ProtectedResource-1

      Resource Name:

      Click the URL listed in the Parent Resource Name list: http://ProtectedResource-1.example.com:1080/*

      The URL is automatically added to the Resource Name field.

      GET:

      Mark this checkbox, and select the Allow value.

      POST:

      Mark this checkbox, and select the Allow value.

    9. Click Finish.

  5. Create a new subject.

    On the New Policy page, in the Subjects section, click New.

    1. Select the subject type and then click Next.

      On the page “Step 1 of 2: Select Subject Type,” select the “Access Manager Identity Subject” type.

    2. On the page “Step 2 of 2: New Subject — Access Manager Identity Subject,” provide the following information:

      Name:

      Enter Test Subject.

      Filter:

      Choose User, and then click Search. Four users are added to the Available list.

      Available:

      In the list, selecttestuser1, and then click Add.

      The user testuser1 is added to the Selected list.

    3. Click Finish.

  6. In the New Policy page, click Create.

    On the Policies tab for users-Policies, the new policy “URL Policy for ProtectedResource-1” is now in the Policies list.

  7. Log out of the console.

  8. Verify that an authorized user can access the Web Server 1.

    1. Go to the following URL:

      http://ProtectedResource-1.example.com:1080

    2. Log in to Access Manager using the following information:

      Username

      testuser1

      Password

      password

      You should see the default index.html page for Web Server 1.

      The user testuser1 was configured in the test policy to be allowed to access Protected Resource 1.

  9. Verify that an unauthorized user cannot access the Web Server 1.

    1. Go to the following URL:

      http://ProtectedResource-1.example.com:1080

    2. Log in to Access Manager using the following information:

      Username

      testuser2

      Password

      password

      You should see the message, “You're not authorized to view this page.”

      The user testuser2 was not included in the test policy tat allows access to Protected Resource 1.