Expand description
WS-Federation Passive Requestor Profile
Implements the WS-Federation 1.2 passive requestor profile for browser-based SSO. WS-Federation is commonly used with Active Directory Federation Services (ADFS) and Azure AD in legacy enterprise environments.
§Protocol Flow (Passive Requestor)
- Application redirects the user to the STS sign-in URL with
wa=wsignin1.0 - STS authenticates the user and posts a security token (SAML assertion)
back to the application’s reply URL (
wtrealm) - Application validates the security token and establishes a session
- Logout: redirect to STS with
wa=wsignout1.0
§Security Considerations
- Federation metadata should be fetched over HTTPS and cached
- Security tokens (SAML assertions) must be validated against the STS signing certificate
- Replay protection via
wctxstate parameter
Modules§
Structs§
- Claim
Type Offered - Claim type advertised in federation metadata.
- Federation
Metadata - Federation metadata for an STS.
- WsFed
Security Token - Validated security token extracted from a WS-Federation response.
- WsFed
Sign InResponse - Parsed WS-Federation sign-in response.
- WsFederation
Client - WS-Federation Relying Party client.
- WsFederation
Config - WS-Federation Relying Party (RP) configuration.
Enums§
- WsFed
Token Type - Security token type.