Administering Cloud EPM: The Platform Beneath the Business Processes · Module 8 · Single Sign-On and Federation
Lab: federate without locking yourself out
Lesson 98 of 201 · 2 min
An hour and a half, and the title is the acceptance criterion. Nine deliverables. A written SSO design for Northwind: provider, domains in scope, username attribute, routing, administrator route policy. SSO configured against a test identity provider in a non-production environment — or, on the follow-along path, a complete configuration runbook with every step and its owner. Evidence: federated sign-in working, AND the administrator route confirmed working. Logout URL configured and tested. A client compatibility test plan covering every client variant Northwind uses, with results or expected results. An automation impact assessment: what runs under what account, and what must change. A user communication draft to send before the change. A rollback plan: what you would do if the change went wrong at eight o'clock on a Monday morning. And a written note on the Module 3 multi-domain decision, revisited: does SSO change your recommendation, and why? The acceptance criteria.…
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 8 · Single Sign-On and Federation
- 1What SSO changes
- 2The sign-in experience under SSO
- 3Configuring an external identity provider
- 4Completing configuration in the console
- 5Multiple identity providers in one domain
- 6SSO across domains in one cloud account
- 7SSO across different cloud accounts
- 8Logout URL and credential management
- 9Making clients work after SSO
- 10What breaksFree preview
- 11Lab: federate without locking yourself out