Identity federation
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design how enterprise, partner, and customer identities trust each other.
Planned topics
- Federation: one system trusts another's login, using standards such as OpenID Connect or SAML.
- Workforce identity comes from the enterprise directory; partners federate their own directory or get managed accounts; customers use a customer identity service.
- Keep the three populations separate: different risk, volume, and lifecycle.
- Map external identities and claims to local roles through a clear, reviewed rule.
Draft outline details
Demonstration
a diagram with three identity sources (directory, partner IdPs, customer IdP) feeding one token service that issues tokens to the platform, with claim mapping at the arrows.
Check your understanding
Why keep customer and workforce identities separate?
Show answer
Different threats, scale, lifecycle, and rules; mixing them widens the attack surface.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.