Tuesday, 10 March 2015

Essbase Read and Write accesses in Security

When I had discussion related to security in Essbase with my friends, to be precise which access between Read and Write takes precedence and when. I had no perfect clue to confess the statement.

I had created one user and took him to the different tests and convinced my self with valid statements, I thought this post will help you as well.

The data looks good and it allows me to do lock and send the data even when I used admin credentials, of course this is known fact! Then

Now I have created user and assigned to one group that has got Read access, Essbase pops me the below box when I tried to lock and send the data using new user credentials.

Group Read access got precedence over user none access.
I gave write access to user still he is part of group that has got Read access now user updated the data.

Now one point is confirmed Write dominates the Read access
User has read access but group has write access
User has write access but group has read access
Now we can add little more confusion to the above points with below statements
When user assigned to two groups one is Read and other is Write access then user access dominates the remaining.
None takes precedence over Read and Write access.
Write takes precedence over Read access.

Thanks for everyone who helped me to write this post and Happy learning :)

1 comment:

  1. head titanium tennis racket
    Head the size of the rest titanium welding of your columbia titanium jacket body. This one fits in a well. where is titanium found It has titanium nose stud a great design and has an overall good titanium lug nuts grip, comfortable

    ReplyDelete