Test a sample header application

Testing a sample header application involves validating application header fields and overall testing. Simulation allows you to validate cookie contents before testing with the back end protected web resource.

Topics

Configure application - Configure the application for simulation testing.
Configure Access Gateway for debug and monitoring - Optionally configure Access Gateway to generate and display debug statements.
Simulation testing - Perform header or policy simulation testing.
Completed application testing - Perform normal application testing using production URLs.
Disable Debug - Disable debug after testing.

Configure application for simulation testing

Note:

This section covers testing using header based simulation and is only required if testing passing of values using application headers.

To configure an application for header or simulation testing:

Navigate to the Access Gateway Admin UI console
From the Topology tab or the Applications tab, open the application.
Select the Settings pane.
Expand the Essentials tab.
Note the current value of Protected Web Resource.

Change the Protected Web Resource field to:

Value	Behavior
`http://header.service.spgw`	When running a test, this displays information about the header, cookie, session, and other information.

Note:

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

Clear the Customize checkbox to disable the post-login URL.
Expand the Advanced tab.
Enable Debug mode.
CAUTION:
When enabling Debug mode, ensure that the download log has also been set to level debug. Application debug events aren't visible in downloadable logs unless download logs are also configured to emit Debug level log events. See Edit log verbosity.
Click Done.
Note:
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.

Configure Access Gateway for debug and monitoring

You can configure Access Gateway Management console to generate a running display of all system log messages.

Open a terminal and use Secure Shell (SSH) to connect to the Access Gateway Management console.
Enter 4 - Monitoring.
Enter 2 - Enable Debug.
Enter 1 - Monitor logs. This starts the running display of all log messages.
Return to the Access Gateway Admin UI console console. You can test your app and examine the results in the running logs.
Enter Ctrl-c to exit the log display.

See Monitor for details about monitoring, including a list of available commands.

Note:

The debug logging level rapidly generates log messages. Always disable debug logging when you've finished examining logging. Otherwise, you may run out of disk space.

Simulation testing

Header and policy simulation testing involves temporarily replacing the Protected Web resource field in an app and then testing various target URLs. You evaluate whether the headers and policies return the expected result.

Configure the app for header or policy simulation testing.
Connect to the Access Gateway Management console and begin monitoring. See Troubleshoot apps.
Select the Applications tab.
On the row containing the app, click Go to application > SP Initiated.
Examine the header or policy information.
Repeat these steps for each protected URI.
When complete, disable debugging.

Completed application testing

Click the Applications tab.
On the row that contains the app, click Go to application > SP Initiated.
Click Go to application > IDP Initiated to run the tests.
Repeat testing using each specialized policy URI.
Disable debugging when you're finished.

Completed application testing as required.

Disable debug

Display debug statements at the command line

Go to the Access Gateway Management console.
Enter [Ctrl]-[c] to exit the log display.
Enter 3 - Disable debug.
Exit the command-line console.

App debug is enabled

Go to the Access Gateway Admin UI console.
Go to the app you're testing.
Expand the Setting tab.
Expand the Essentials tab.
Return the Protected Web Resource field back to its original value.
Expand the Advanced tab.
Set the Debug toggle to Disable.
Save your changes.