SSO Doctor

All troubleshooting guides

SSO troubleshooting evidence checklist: collect useful data safely

By SSO Doctor · Technical guide

A useful SSO escalation connects one failed attempt to an exact error, a timestamp, the application and identity provider involved, and independently confirmed expected values. Share a sanitized reproduction through an approved channel instead of sending a raw browser capture.

Start with this checklist

Choose evidence for the protocol

For SAML, preserve the relationship among request, response, audience, endpoints, timing, and trust material. For OIDC, distinguish the ID token from an access token and record the relevant expected issuer and audience. For SCIM, record the operation, HTTP status, and sanitized error details. Do not assume an authentication failure and a provisioning failure have the same cause.

Review sensitive data before sharing

Exclude passwords, client secrets, private keys, session cookies, refresh tokens, and live bearer credentials. Logs and captures may also contain personal information, authentication codes, and sensitive query strings. A HAR file can contain much more than the failing request. Follow your organization’s handling policy and inspect the complete artifact, including headers and embedded payloads.

Replacing identifiers consistently can preserve a comparison: use the same placeholder wherever the same value occurred, and distinct placeholders where values differed. Preserve relevant structure and mark every replacement. Redaction does not guarantee that an artifact is safe to share.

Sanitization changes what can be verified

Editing signed XML or a JWT changes the signed content. Use a sanitized artifact to explain structure or comparisons, and label it as modified. Perform cryptographic verification against the original only within an authorized environment, or create a fully synthetic signed test fixture. A sanitized reproduction cannot establish that the original signature was valid.

Copyable escalation template

Application / environment:
Protocol / sign-in route:
Observed error:
Failure time / timezone:
Request or correlation ID:
Affected scope:
Recent changes (unconfirmed context):
Observed values:
Expected values and authoritative source:
Sanitization performed:
Checks already completed and results:
Unknowns / requested next verification:

Bring bounded evidence to SSO Doctor

SSO Doctor analyzes supported SAML, OIDC/OAuth, SCIM, and WS-Fed evidence. Supply known expectations explicitly and leave unknown configuration unknown. The free SAML Decoder and JWT / OIDC Inspector are accessible under Free Tools. Inspection alone does not establish trust or prove an end-to-end sign-in works.

Reference

OWASP Logging Cheat Sheet: data to exclude provides guidance on sensitive information in logs. Apply your organization’s policy to collection, retention, and sharing.

Related guides