Authentication integration reference
Evaluate one deployment-specific access path with named versions, policy ownership and failure handling.
Windows and VPN
Start Windows testing with an enrolled user returning to a locked managed workstation. Initial Windows sign-in and RDP are separate scenarios. For RADIUS or VPN, record the gateway and firmware, configured policy and timeout behavior, then show who enforces access.
Federation and Microsoft identity
For configured OIDC, SAML or Keycloak integrations record issuer, registration, claims, logout and who owns the session. For Microsoft Entra or Microsoft 365 record where authentication is requested and how policy applies. A specific Entra External MFA or Conditional Access claim requires evidence for the named setup.
Representative acceptance
For each route record version and configuration, normal login, decline or timeout, revocation, device recovery and operator responsibilities. Keep application-ready, rejected and pending outcomes distinct.
Data and operations
Keep the deployed credentials and tenant secrets out of screenshots and support tickets. Record a synthetic request identifier and the observed outcome. The application, gateway or endpoint remains responsible for access.
Pilot record example
Access path: managed workstation unlock. Conditions: already-enrolled synthetic user, locked workstation, approved network. Expected outcomes: normal unlock, denial after a declined request, and documented support route when the device is unavailable. Assign the endpoint team the enforcement checks and the authentication team the enrollment and event review.
Evidence for a new gateway
Ask the gateway owner for a named product and firmware version and the authentication team for the server and client versions. Have the operator show a normal decision, a decline and an unavailable authentication service. Record what the gateway does in each case and who can change that policy.
