Hyperion Shared Services Active Directory

Question

Gurus, i am an Essbase Developer and currently have an issue where the users in the Hyperion Shared Services Active Directory does not reflect the true number of users actually on the company network.
Whilst new employees created in the company flow through correctly into Hyperion Shared Services, those who have left the company still show in Hyperion Shared Services, even though they have been deleted from the network. Its as if newly created users synchronize perfectly into the Hyperion Shared Services Active Directory, but the deletion of users does not flow through.
Has anyone experienced this?
Thanks

Answer 1

Hi,
You are fecthing the user ids from Active Directory just to reduce lot of manual effort of creating native ids for all the user and also a security part its suggested to use Active Directory.
Now how can you say that id is still active in AD, the user who had left the company his id would be already inactive even though you are able to query the user and provision on his id or add him/her to a group that has provisions will not be able to login as their id is made inactive.
If you want to remove them automatically from Essbase or Shared Services automatically when their id gets disabled it wont happen as provisioning information etc lies with Shared Services and just to authenticate a valid user AD comes into picture .
If you want to eliminate users from accessing the system whose id is disabled is to change your AD configuration in Shared Services based on the inputs from your AD team such that where does the disabled id go into (ex : which OU etc..) and configure accordingly which should work.!!! now if you want to eliminate them from Essbase unprovision them/their ids and run security refresh .
Thanks
Amith