Essbase Security Implementation
Essbase Security Implementation
“Implementing Security in
Oracle Hyperion Essbase using Shared Service”
Description:
This document provides an overview of security model of Hyperion Essbase
using Shared Service. It also focuses on cell level security using Essbase filters
and common administrative activities associated to user/group
administrations.
History:
Version Description Author Publish Date
Change
0.1 Initial Draft Gaurav Shrivastava 30-Mar-2011
0.1 Review I Amit Sharma 1st April
Table of contents
1) Introduction
2) Launching Shared Service
3) Converting Security Mode
4) Benefits of externalizing the security:
5) Working with Shared Service
a) Creating Group
b) Creating User
6) Add new Role
7) How to create user through maxl?
8) Refresh Security from Shared Services
9) Apply Provision
10) Creating Filter
a) Read Write Filter
b) Read Filter
c) Meta Data Read Filter
d) Read and No_access Filter
e) Read Write and No_access
f) Metadata Read and write filter
g) Filter on member Combination
h) Filter on member Combination Separately
11) Administration Option
12) Configuring User Directories
13) Recover Native Directory
14) Configure Auditing
15) Assign Access Control
16) Understanding Roles
a) Shared Service Roles
b) Essbase Roles
This is the shared service console by you can manage all Hyperion products. You can perform all
administration tasks through this console such as user creation, user deletion, assigning roles managing
Converting Security Mode: The default Essbase security mode is 'internal security' model. In this
model, we see Essbase creating users, managing their passwords, and their access all within the Essbase
product. Essbase uses Essbase.sec file to store security information locally in Essbase. It is therefore
possible to have an Essbase server not manage roles and access via Shared Services, but that option is
becoming increasingly uncommon. Its main use is for legacy Essbase servers to 'migrate' users from
their legacy versions into the System 11 world of Shared Services.
Alternatively we can externalize the security and let Shared Service manage the security for Essbase.
Creating Group
Right click on “Groups” and select “New”
Give group name and insert description about group then click next.
Success message
Creating User
Open shared service expend user directories then native directory.
Right click on user and click new
Success message
Verify that access rights correctly assign to the user. When you login with the same user it will show
only “Bisp” application.
If you made changes for current user select current user else select refresh security for all users.
Click ok…
Success massage
Apply Provision
Through shared service you can apply provision to particular user. Right click on user
Select desired roles from the available roles and save the changes.[List of roles are given in appendix]
You can validate that “ram1” can access only “Bisp” and “Sample” application.
Now log off from the existing user and login through new user “Tom”.
You can verify through right click on “Bisp” application and find that “Tom” is not administrator so that
some options are disable.
You can verify that user “ORG” has access rights to write on “Budget” through lock and send method.
Again load data in actual field through lock and send method.
When you update data in actual field and then try to lock it Essbase throw the below error.
Connect to “BispBD” database and try to update or write on “New York” data through lock and send
method. Essbase will throw the below message.
You can verify that “ORG” user should not access data other then “New York”.
Execute the Maxl script and see the impact on excel login through the user.
Database is modified.
Open application databases then assign filter to the user and click apply.
User also has update write, So update any value through lock and send method.
To verify that data get updated or not “Retrieve” and check updated cell.
Below Maxl script for creating filter and assign to the user.
You can access complete data which has either “Cola” or “New York”.
Select database
Select at least one user and click on Right check mark to validate settings.
Directory Manager: Creates and manages users and groups within Native Directory.
Do not assign to Directory Managers the Provisioning Manager role because combining these roles
allows Directory Managers to provision themselves. The recommended practice is to grant one user the
Directory Manager role and another user the Provisioning Manager role.
LCM Manager Runs the Artifact Life-Cycle Management utility to promote artifacts or data across
product environments and operating systems. LCM utility also use for migrate application on the same
environment or different environment.
Project Manager Users who are assigned the Project Manager role can create and manage projects
within Shared Services
Application Creator Creates and deploys Performance Management Architect applications. Users with
this role can create applications, but can change only the dimensions to which they have access
permissions. Required, in addition to the Dimension Editor role, for Financial Management and planning
users to be able to Navigate to their product’s Classic Application Administration options. When a user
with Application Creator role deploys an application from Performance Management Architect, that
user automatically becomes the application administrator and provisioning manager for that
application. The Application Creator can create all applications.
Analytic Services Application Creator: The Analytic Services Application Creator can create Generic
Performance Management Architect applications.
Financial Management Application Creator: The Financial Management Application Creator can create
Consolidation applications and Performance Management Architect Generic applications. To create
applications, the user must also be a member of the Application Creators group specified in Financial
Management Configuration Utility.
Planning Application Creator: The Planning Application Creator can create Planning applications and
Performance Management Architect Generic applications.
Essbase Roles
Power Roles
Administrator Grants full access to administer the server, applications and databases
Application Manager Creates deletes and modifies databases, and application settings within the
assigned application. Includes Database Manager Permissions for the databases within the assigned
application
Create/Delete Application Creates and deletes applications and databases within applications. Includes
Manager Permissions for the applications and databases created by this user
Database Manager Manages the databases, database objects, locks and sessions within the assigned
application Load/Unload Application Start and stops an application or databases.
Interactive Roles
Calc: - Calculates, updates and reads data values based on the assigned scope, using any assigned
calculations and filter
Write: -Updates and reads data values based on the assigned scope, using any assigned filter
Filter: - Accesses specific data and meta data according to the restrictions of a filter
View Roles
Read: - Read data values
Server Access: - Accesses any database that has a default access other than none