Test SharePoint integration

During this task you will final test the SharePoint integration. Testing a SharePoint application involves validating round trips using both SP or IDP tests.
Testing SharePoint typically includes:

  • Login to SharePoint.
  • Ensure you are prompted for an Okta authentication.
  • Validate SharePoint functions as expected after the integration.

Topics

Configure application debug

To enable debug for application 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 Advanced sub-tab.
  5. Set the Debug toggle to Enable.
    The debug toggle, which can be found in the Advanced application settings.
  6. Click Done.

    When debugging 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.

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

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

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.

Test

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

Disable debug

Display debug statements at the command line

  1. Go 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.

App debug is enabled

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

Next steps

Kerberos application troubleshooting and best practices