Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Implementing SSO for Internal Employees
Content
Hello,
We're gearing up to begin a project to implement SSO for our internal candidates in the near future. I'd like to hear from others in the community that have done this after operating without candidate SSO for a number of years. What major issues should we be aware of? Any particular pitfalls?
Here's what I've come up with so far:
- Clean up the database. Has anyone done this? Lessons learned? Tips or tricks to doing it quick and easy?
- We have 30,000+ candidates in our database today with a company email address. Since our company reuses email addresses (ugh!) and our instance used to be configured to allow multiple uses of the same email address (double ugh!), We need to run some clean-up activity to merge duplicate profiles, populate correct employee IDs on active employees, and "terminate" profiles of individuals that are no longer employees by replacing the company email and stripping the internal indicator (if present).
1