KB273717: When restricting user access using the Project Access part in Project Configuration, the security does not get applied correctly in MicroStrategy Object Manager 10.x.

SUMMARY:
This issue has been classified as a defect by Strategy. The impact is from the Strategy 10.1 product when restricting user access using Project Access within Project Configuration, the security does not get applied correctly in Strategy Object Manager. A solution/code fix for this issue is not available in current releases but is being reviewed for a future Strategy release.
 
SYMPTOM:
After revoking permissions for one project for user using security roles, it will be noticed that the permissions provided are not reflected in Strategy Object Manager as the user can see all the projects.
 
STEPS TO REPRODUCE:

1. Set the Strategy Tutorial project access for the Normal Users security role to only allow two groups (Architect group and Object Manager group) by going to Project Configuration – Project Access - General.

1. Set the Human Resources Analysis Module access to not allow any group.

1. Grant Architect privileges for the Architect group.

1. Grant Object Manager privileges for the Object Manager group.

    - Take note that in both cases, they seem to be correctly applied to only the Strategy Tutorial project.

1. Create a user that belongs to both groups (Test1)

1. Log in Developer as the Test1 user and notice that the user can only see the Strategy Tutorial as expected.

1. Log in Object Manager with the same user and notice the user is able to see all the projects.

 
CAUSE:
This is a known issue in Strategy Object Manager 10.1.
 
ACTION:
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release.