Use groups from active directory for EPBCS application access
SummaryWe need to use groups created in active directory, to provide access in EPBCS application, rather than creating native groups.
We need to use groups created in active directory, to provide access in EPBCS application at dimension/form level, rather than creating native groups. This would reduce the maintenance effort required to maintain groups in AD as well as native directory. This is possible on current Hyperion on-premise applications. Following is the current process for on-premise Hyperion applications and business benefits:
Using Native groups in Hyperion:
Our Organization has several Hyperion applications with more than 200 users using these applications. Currently we use native groups to provision access for Hyperion applications. For any user that requires access to the Hyperion environment, user has to raise a request through SailPoint (access request system). User has to select what group he requires access through SailPoint and once the request is placed, it goes through an approval workflow for the group/application owner to confirm the request. Once the request is approved, IT assigns this request to a Hyperion support person who adds this user to the Hyperion native group