OBIEE - Manage Privilege - Upgrade Stability

Matt Van Asten

Organization Name

Southern

Description

We are using "Manage Privileges" under OBIEE Administration > Security to secure access to different roles created for the organization. For example, we have create different Admin role types to manage different components of OBIEE. However, after an upgrade (i.e.v confirmed impact during 20B to 20C, 20C to 20D), the "Manage Privileges" custom settings are being reset to default. An upgrade does not keep the client's setting. We have to manually reset the "Manage Privileges" after each upgrades.

Examples:

Access "Access to Administration" is restricted to a client  "XX BI Administrator Role" as 'Granted' instead of "BI Administrator Role" to further restrict access to Administration components across the HR and FIN Teams.  The 'BI Administrator Role' is removed from the setting. However, after an upgrade, the "BI Administrator Role" is reset as 'Granted' and the  "XX BI Administrator Role" is no longer part of the setup in "Manage Privileges"

 

Time to reset after each upgrade per POD: 1-5 hours

Expected behavior: The client's setting should not be reset after each upgrade for OBIEE "Manage Privileges."

 

 

 

Use Case and Business Need

The use case is for an upgrade not to erase client specific settings in OBIEE under Administration. We are confirming that other components like SFTP setup are not being impacted. The Administration > Security > Manage Privileges controls key settings for client to secure their OBIEE application and should not be impacted by an upgrade.

 

 

More details

The manage privileges of OBIEE should be 'update safe.' A client should not have to reset each of their FA pod after an upgrade.

Original Idea Number: 2d0c3ed91f