You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Security

edited Sep 16, 2021 12:16PM in Recruiting, Opportunity Marketplace 6 comments

Hello Experts,

Our organization is transitioning from Taleo to ORC, and we are reviewing our system security options. Recruiting is our final HCM module for full integration, so we already have HCM security in place. Currently, our security is based on IP Whitelisting, so our environments are quite closed.

This presents a problem for internal applicants and external pending workers who require access to our environment outside our corporate network. As a result, we've been investigating LBAC security which removes IP whitelisting and grants permissions based on security roles.

My questions:

  1. How are your organizations navigating system security for Recruiting: completely open, IP whitelisting, or LBAC?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!