Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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.

Global search / Oracle Search & data security

Summary: Global search / workers LOV search etc not adhering to security profiles


Content (please ensure you mask any confidential information): Is it expected behaviour that the global search and the workers searches (in employment info, once oracle search for redwood has been enabled for example) no longer adhere to the security policy held against the role?

It is only the LoV that is affected, but all workers are returned, irrelevant of security profiles. For example we have a use case where workers from one BU should not see workers from another BU - we have secured this by AoR successfully till now. After enabling the enhanced global search, the LoV returns everybody within the whole enterprise regardless of the security. You cannot access their pages, but can see their name / picture / title etc in the LoV. Not what we expect or want.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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