Closed as fixed if next.
A person may be deemed as sensitive and so can only be viewed by a select group of persons or person. The sensitivity function needs to be customizable by customers therefore an API is necessary.
Provide customization point for Participant Sensitivity check
This APAR has been addressed in 188.8.131.52: Previously, there were no customization point for Participant Security check. A new interface - curam.core.impl.InternalUserSecurityHook and a default implementation class - curam.core.impl.InternalUserSecurityHookImpl have been introduced in OOTB to support this. The implementation logic inside the else block of curam.core.impl.ParticipantSecurityCheck.authorize() has now been moved to the new class. Customers who want override the authorize method have to create a new class that implements InternalUserSecurityHook interface and provide implementation to the authorize method bind the new implementation in their Module class For example, in their own Module class, bind(InternalUserSecurityHook.class).toInstance(new MockInternalUserSecurityHookImpl()); By default, the OOTB implementation is executed. After the new implementation class is bounded, it will be called. To load their new Module class, customers should add a row to MODULECLASSNAME table in the database using a custom DMX file. More details can be found in chapter 5 of Persistence Cookbook guide.
Reported component name
CURAM SOCIAL PG
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels