Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access
Single sign-on, briefly
Lesson 99 of 184 · 2 min
What it changes about your job, what it does not, and THE FAILURE MODE WHEN THE IDENTITY PROVIDER IS DOWN AND NOBODY CAN GET IN. Single sign-on moves authentication out of EBS: the identity provider decides who somebody is, and EBS accepts that answer. WHAT CHANGES IS PASSWORDS AND LEAVERS, AND BOTH ARE IMPROVEMENTS. Lesson 6's policy stops being yours — one password across every system, which is genuinely better for the person and removes the note under the keyboard. And a leaver disabled centrally loses access to everything at once, which closes Lesson 8's first failure structurally rather than by remembering. WHAT DOES NOT CHANGE IS EVERYTHING IN THIS MODULE EXCEPT AUTHENTICATION. Responsibilities, menus, exclusions, operating units — all still EBS, all still yours. Single sign-on answers "who is this" and says nothing about "what may they do", and Lesson 2's six checks are unchanged. AND THE FAILURE MODE…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 9 · Users, responsibilities and access
- 1Users, responsibilities and menus
- 2Why a user cannot see a function
- 3Operating units and access
- 4End-dating rather than deleting
- 5The requests you should refuse
- 6Password policy, and what it is worth
- 7Single sign-on, briefly
- 8What breaks: three access failures
- 9Lab briefing · Diagnose four access complaints