Administering Cloud EPM: The Platform Beneath the Business Processes · Module 7 · Provisioning at Scale
Synchronizing across identity domains
Lesson 80 of 201 · 14 min
The use case — Module 3's multi-domain estates, and estates spanning cloud accounts. Configure synchronization from a source domain to a target domain, run the initial synchronization, verify users and groups in the target, add a user in the source and show it propagate — then remove a user in the source and show THAT propagate. THIS IS THE MITIGATION FOR A MULTI-DOMAIN ESTATE, and it is worth knowing before you conclude in Module 3 that multiple domains are unmanageable. They are manageable; they are just more work. TEST THE REMOVAL PATH SPECIFICALLY. Propagation of additions is what everyone checks; propagation of removals is what auditors check.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Provisioning at Scale
- 1Why manual provisioning fails
- 2What synchronization does and does not carry
- 3Synchronizing across identity domains
- 4Synchronizing specific users and groups
- 5Synchronizing from an external directory
- 6Groups for application-level role assignment
- 7Password policies
- 8Email notifications and password resets
- 9What breaks
- 10Lab: design the synchronization and test the leaver
