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.
Has anyone set up Single Sign on (SSO) with Equest?
Summary:
We are a large company with a decentralized recruiting process/team. There are instances where we do not want everyone to be able to access Equest even if they share the same security role
Content (required):
With a decentralized recruiting process we already have a fair amount of security roles and we did not want to duplicate solely for Equest posting permissions. We have tried to work with equest to understand how to implement SSO but have not gotten anywhere. We would like it so if a recruiter clicks on the job distributer link, they will not be able to access equest if they do not have access Has anyone else had any luck with implementing SSO with Equest?? Or any other thoughts on how to solve this issue?
0