Web Services Connector | Provisioning | Order of HTTP Operations

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I am seeking some clarity on how various HTTP Operations are executed by IDN during Provisioning to a WSC Source.

Say, we have a WSC Source and there are 4 types of entitlements (ET1,ET2,ET3,ET4). All of these 4 are configured under Entitlement Types and Source Account Schema has 4 multi-valued attributes for each of the ET#.
Following HTTP Operations are configured, in the same order they are here:

  • Account Aggregation
  • Group Aggregation for each type of entitlement
  • Single Account Aggregation
  • Add Entitlement and Remove Entitlement set individually for each type of entitlement

Now when a user is granted multiple entitlements (from different ET#) from this source and user does not have an account in the Source, is this the right order of flow of HTTP Operations:

  • Create Account
  • Add Entitlement-ET1
  • Add Entitlement-ET2
  • Add Entitlement-ET3
  • Add Entitlement-ET4
  • Single Account Aggregation

Any help or links to more read will be appreciated

2

Hi Nithesh,

This will depend on how you have configured your Create Account Operations. So now it depends on what your target supports. So if it supports Create Account without Entitlements then you should configure your Create Account as Primary and then others as dependent operation. Also mark the createAccountwithOperation as false.
This order should work :

  • Create Account
  • Add Entitlement-ET1
  • Add Entitlement-ET2
  • Add Entitlement-ET3
  • Add Entitlement-ET4
  • Single Account Aggregation

Let me know what is the issue you are facing.

1 Like
3

Thanks @RAKGDS

The End system supports all types of operations - Create Account, Add Entitlements or Both in single operation. However, we would like to keep them as separate operations

Not sure how do I make the following Entitlement Add Operations dependent on Create Accout?

4

Hi Nithesh,

So, try Create Account operation. if you are not able to see that you can use API to add that and will see it and then add your Entitlement one after the another(make sure the operation name are different).

Let me know if you need more details on the same.

Thanks
Rakesh Bhati

5

Thanks @RAKGDS

Let me try this out…

However, I am just wondering why is Add Entitlement - ET# not automatically called when the Provision Plan has Entitlement Type ET# Attributes as Add

Sorry I did not answer your earlier question: Issue is that after Create Account none of the Add Entitlement - ET# is called even if there are entitlements from multiple ET#s

6

Have you uncheck createAccountwithEnt in the configuration part ?

7

@RAKGDS
I don’t see such an option… Where do I find it?

image
image1266×558 16.8 KB

8

Hey Nithesh,
The setting is under Additional Configuration.

WindowsConnector
WindowsConnector1441×873 46.1 KB

10

Yes, should this be checked for Add Entitlement - ET# to be called post Create Account operation?

11

No Nithesh, it will be the reverse if your Create Account does not contain Entitlements and you want that Add Entitlement should be called after Create Account operation.

1 Like
12

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.