Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

Entitlement for Service’s / Catalog item’s & Actions are NOT working when LDAP group is imported

$
0
0

Hi ,

 

I have VCAC 6.2.4-3624913 build and IDM as Identity source.  I am trying to configure entitlement for one business group which is created in IDM. VCAC is able to lookup new group created in IDM. Please find below example , Issue description : , Requirement &  Observation.

Kindly advise if you have such scenario. I have right of Tenant administrator

 

User sam@example.com who is member of   IDM group “network-l3-team”

 

Issue description : 

Entitlement are not correct when we configure IDM  group  in Business / Entitlement & Custom groups.

If we import group IDM group “network-l3-team”  for which  User sam@example.com is member then we  found that allocated entitlement are not visible  once SAM is login using his domain account.  Rather only Home tab is visible. 

 

Requirement: 

We have to configure user who is responsible to consume only IT services so we have imported network-l3-team  group in   user area while configuring  Business Group.

 

Observation:

 

Entitlement for Service’s / Catalog item’s & Actions are working perfect when Domain User (sam@example.com) added at following places

  • Business Group with User Role:  Import LDAP user sam@example.com
  • Entitlements:  Import LDAP user sam@example.com . Limited entitlement allocated in terms of services, actions & catalog items.  Entitlements are correctly allocated according to the services selected and their respective catalog items.
  • Custom Groups:   Import LDAP user sam@example.com.

 

 

But

 

Entitlement for Service’s / Catalog item’s & Actions are NOT working when LDAP group is imported at following location

 

 

 

 

Kindly advise if any one   face such issue.


Viewing all articles
Browse latest Browse all 9859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>