Issue in Provisioning to main account the Associated Entitlements

[kmashwini]

Hello All,

We have configured Associated Entitlement, after provisioning the associated entitlement mapping to secondary AD account and not mapping to primary account. In AD endpoint, we have mentioned Primary account types also but still associated Entitlement goes to secondary account.

Please let me know any additional config need to be done.

[NM]

Hi @kmashwini , is both the account present in same endpoint .?

[kmashwini]

@NM Yes for same endpoint we have primary and secondary, also in endpoint we have given only primary account type filter.

[rushikeshvartak]

• it will only add in secondary account, after recon it should add in primary

[kmashwini]

@rushikeshvartak  Even after recon still the entitlement is mapped in secondary account only and not moved to primary account.

[NM]

@kmashwini goes sec and primary account have different name? And are they 2 seperate account on target if so it won't map the entitlement to primary account.

[kmashwini]

@NM Yes they both are 2 seperate account in target . How do I get entitlement to primary account when I am requesting entitlement (Endpoint C) which has assocaited entitlement (Endpoint A) .

[NM]

When you request for endpoint c does it create 2 task for both primary account and secondary account present under endpoint a? Or only for one ?

2) use analytics to provision the entitlement to primary account id endpoint C

[kmashwini]

@NM It creates one task for Endpoint C which is required and another task it created for secondary account (endpoint a) which is wrong we need for primary account in endpoint A . How do we achieve this? Even in Endpoint A we have specified only primary account type in filter.

[rushikeshvartak]

Can you elaborate your problem statement with example 

[kmashwini]

@rushikeshvartak @NM  Use Case is we have two endpoints A and C. Where in Endpoint A has primary account type and Secondary Account type. Here we are requesting access for Endpoint C which has associated entitlement of endpoint A. Task are getting created for endpoint C and endpoint A , but in Endpoint A we are getting add access created for secondary account instead of primary account. How do we can resolve the issue?

[rushikeshvartak]

• Its seems its random and can't control this , Use analytics instead of associated entitlements