Identity boundaries
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
define identity for users, services, and partners across the merged organizations.
Planned topics
- Three identity types: people (customers, staff), workloads (services), and partners (external systems); each has its own lifecycle and credentials.
- Decide the authority for each type: one identity provider for staff, a workload identity system for services, a partner onboarding process.
- Federation lets one provider trust another without merging user stores; plan it before consolidation.
- Separate authentication (who) from authorization (what they may do).
Draft outline details
Demonstration
Table: identity type | authority | credential form | lifecycle | who can revoke. Example: service | workload identity issuer | short-lived token | tied to deployment | platform team.
Check your understanding
Why separate authentication from authorization?
Show answer
Knowing who a caller is does not decide what they may do.
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.