Administering Cloud EPM: The Platform Beneath the Business Processes · Module 8 · Single Sign-On and Federation
The sign-in experience under SSO
Lesson 89 of 201 · 1 min
What a normal user sees: a company sign-in route — and in an integrated Windows authentication setup, possibly no prompt at all. What an administrator sees: the company route, PLUS a traditional cloud account route, needed for client components. DO NOT REMOVE THE ADMINISTRATOR ROUTE CASUALLY. It exists for a reason, and the reason is the previous lesson. And the part that is not configuration at all. A changed sign-in experience generates support volume unless it is communicated. Draft the message BEFORE the change, not after. The bookmark problem. Users have bookmarks. Some will still work, some will not. Test and communicate — and note that "some will still work" is the awkward case, because it means the failure looks random from the user's side.
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