Cloud identity federation is the practice of extending trust across organizational and cloud-platform boundaries so that users authenticate once β in their own identity provider β and gain access to resources across AWS, Azure, GCP, and SaaS applications without maintaining separate credentials in each system. It sits at the intersection of security architecture and user experience: done well, it eliminates credential sprawl and accelerates onboarding; done poorly, it creates invisible blast radii where a single compromised signing certificate unlocks every federated application at once. The critical mental model is that federation shifts risk from password hygiene to trust-relationship integrity β your attack surface is now your IdP signing keys, your role trust policies, and your claim validation logic, not individual passwords.
What This Cheat Sheet Covers
This topic spans 17 focused tables and 129 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Federation Protocols Compared
The three major federation protocols β SAML 2.0, OpenID Connect, and WS-Federation β cover different eras and use cases of enterprise identity. Choosing the wrong protocol forces workarounds; knowing when each one still applies is one of the most practical decisions in identity architecture.
| Protocol | Example | Description |
|---|---|---|
<samlp:AuthnRequest> Destination="https://idp.example.com/sso/saml" AssertionConsumerServiceURL= "https://sp.example.com/acs"/> | XML-based open standard for browser SSO; uses signed assertions with three statement types: AuthnStatement, AttributeStatement, and AuthzDecisionStatement; dominates enterprise SaaS (Slack, Salesforce, Zoom). | |
GET /authorize?response_type=code &client_id=CLIENT_ID &redirect_uri=https://app.example.com/cb &scope=openid+email+profile | Lightweight identity layer on OAuth 2.0; uses JSON Web Tokens (JWTs) instead of XML; preferred for modern, API-first, and mobile applications; becoming dominant in cloud-native and CI/CD federation. | |
GET /adfs/ls/?wa=wsignin1.0 &wtrealm=https://app.example.com &wctx=session%3Dabc123 | Microsoft-origin protocol for browser-based SSO (Passive Requestor Profile); underpins legacy SharePoint, Exchange, and ASP.NET apps built on Windows Identity Foundation; still in wide use in hybrid Microsoft environments. |