In most instances, unexpected results are caused by one or more missed steps in Developing Native Web Applications.
This section describes accessing Adaptive access events either by the Events service API or Adaptive access reports and using the event detail to troubleshoot steps that may have been missed and other error causes.
Events are generated when an Adaptive access policy assigned to a native application is invoked for a Post authentication rules evaluation.
When determining where to start the troubleshooting process, is helpful to understand these steps cumulative. You can skip directly to the event type observed for your scenario.
Before you begin troubleshooting is it recommended to check the System status for known service interruptions that may impact Adaptive access collection, detection or Adaptive access policy evaluation.
The event ordering for troubleshooting is:
- System status
- Successful evaluation
- No event or report
- Risk Service Unavailable
- Unexpected evaluation decision
- IBM Security Verify tenant hostname.
- IBM Security Verify Adaptive access snippet host and snippet ID.
- At least one Session ID.
- Correlation ID from event or report.
- IBM Security Verify client_id (do not provide the secret).
- IBM Security Verify application id or name.
My Native Web App
- IBM Security Verify Access policy id or name.
My Native Web App Adaptive access policy
If the troubleshooting process does not resolve your error, refer to the IBM Security SaaS Support topic under the Troubleshooting and support section of the IBM Security Verify product in the IBM® Knowledge Center.
Next: System status