These actions show the kind of ticket and vendor language a saved report can produce.
Technical Findings
What AccessTrace would flag
1
HTTP errors found in browser trace
MEDIUMMEDIUM confidence
The HAR contains failed HTTP requests during the login flow. In SSO troubleshooting, 400/401/403/500 responses often identify the point where the browser flow breaks.
Recommended remediation
Correlate the failed URL and timestamp with IdP, SP, reverse proxy, and application logs.
Sample evidence
POST https://app.example.edu/saml/acs -> 400
GET https://app.example.edu/login/callback -> 400
2
Large request headers detected
MEDIUMMEDIUM confidence
Large cookies or request headers can trigger Bad Request errors at the application, web server, proxy, or load balancer layer.
Recommended remediation
Review cookie size, request header limits, and whether old session cookies are accumulating.
Sample evidence
Cookie header length: 9120 characters
Error occurred on ACS/callback endpoint
Sample Generated Report
Troubleshooting narrative
Executive Summary
The HAR indicates that the SSO flow reaches the application callback/ACS endpoint but fails with HTTP 400. Large request headers are also present, which may explain a Bad Request response.
Most Likely Root Cause
The application or an upstream web component may be rejecting the request because the request headers/cookies are too large, or because the ACS/callback request is malformed.
Recommended Next Step
Correlate the failed browser request with application and web-server logs. Check request header size limits and clear stale cookies before retesting.