Configure applications for testing



Under normal circumstances, the Protected Web Resource field of an application defines the resource being protected.
However, you can use this to configure applications to behave like a sample header or sample policy application and provide general troubleshooting and diagnostic information.

Topics:

Configure

To configure an application for header or policy simulation testing:

  1. Navigate to the Access Gateway Admin UI console
  2. From the Topology tab or the Applications tab, open the application.
  3. Select the Settings pane.
  4. Expand the Essentials sub tab.
  5. Note the current value of Protected Web Resource.
  6. Change the Protected Web Resource field to one of the following:
    ValueBehavior
    https://header.service.spgwWhen running a test, results in the display of information related to the header, cookie, session, and other information.
    https://policy.service.spgwWhen running a test, results in the display information related to application policy.
    Important Note

    Important

    Copy and save the original back end Protected Web Resource value.

  7. Expand the Advanced sub-tab.
  8. Set the Debug toggle to Enable.
    The debug toggle, which can be found in the Advanced application settings.
  9. Click Done.
  10. Tip

    Tip

    When debugging header based applications: Consider testing attributes with static known good values. For example, change dynamic IDP based fields to static with known good values.
    When debugging policy based applications: Test with no policy or open policy first.

Monitor using the Access Gateway Management console

  1. Open a terminal and using SSH connect to the Access Gateway Management console for example.
    ssh oag-mgmt@gw-admin.<domain.tld>
    or
    ssh oag-mgmt@gw-admin.mysite.myco.com
  2. Login using the default or a previously set password.
  3. Navigate to the log monitoring page:
    1. Enter 4 - Monitoring.
    2. Enter 2 - Enable Debug.
    3. Enter 1 - Monitor logs.

    The a running display of all log messages will begin to display. Return to the Access Gateway Admin UI console console and exercise the application being examined.
    See command line Access Gateway Management console/monitoring for a complete list of all monitoring and related commands.

  4. Enter [ctrl][c] to exit the log display.
  5. Enter 2 - Disable debug.
Important Note

Important

The debug logging level rapidly generates log message. Be sure to always disable debug logging when you have finished examining logging.
Failure to disable debug logging could result in rapid log file growth and out of disk errors.

Test - Policy

  1. Select the Applications tab.
  2. On the row containing the application, click Goto application > SP Initiated.
  3. If required, sign in.
    Results are displayed depending on which application type was selected header or policy.
  4. For policy based testing, update the URL to add an appropriate path and resend the request.
    In this example, the /public path was added.
  5. The result of applying the current user and policy is displayed.

Test - Header

  1. Select the Applications tab.
  2. On the row containing the header application, click Goto application > SP Initiated.
  3. If required, sign in.
  4. Examine Access Gateway Management console window for errors, or log events.
  5. Examine the result of the test.
Important Note

Important

When the Debug mode is activated on production applications, it can impact the performance. When complete, always reset the Protected Web Resource field and deactivate the Debug mode toggle.

Disable debug

  1. Return to the Access Gateway Management console.
  2. Enter [ctrl][c] to exit the log display.
  3. Enter 3 - Disable debug.
  4. Exit the command line console
  5. Return to the Access Gateway Admin UI console
  6. Navigate to the application being tested
  7. Expand the Setting sub tab.
  8. Expand the Essentials sub tab.
  9. Return the Protected Web Resource field back to its original value.
  10. Expand the Advanced sub tab.
  11. Set the Debug toggle to Disable.
  12. Save your changes.