Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new
Hi,
I am trying to create source account using create account api in a web service connector. but in the api, there are some mandatory fields like policy id, sponcer id which is different for all users. How can I create it?
Map the attributes in the provisioning plan to identity attributes.
Make those identity attributes if they don’t already exist
Create transforms to convert existing values from other sources to values that you need in the provisioning plan/identity attributes
Hi @phil_awlings ,
in the attached screenshot i need the values to create the source account. but the stroked one are the values which user is giving in servicenow request later. I can get the firstname, lastname, mailid from identity attribute. But other field are different for all users. Means user A will raise a request with security policy xyz1, and user B will raise a request with security policy xyz2. and the source account has to be created with respective values
have you configured provisioning policy and also create body in ISC?
No I have not set it up yet. I want an idea how to proceed for this type of scenario for create account source
The same thing what we do primarily with postman, for create account there should be mandatory fields to create.
In ISC
You need to create provision policy
Create account API end point with required payload, this should be done under HTTP operations
The following document will help you.
“in the attached screenshot i need the values to create the source account. but the stroked one are the values which user is giving in servicenow request later”
Clarity: The attributes that you need to populate in the CREATE request on this WS connector are provided by ServiceNow later on?
IIf that is the case the, you will have to create the ServiceNow account first. Make the presence of that sub-account a criteria in provisioning the WS account.
If that is not the case, then I don’t understand the problem statement. Sorry
Let me reframe the problem again. The user create account api which application team has provided that has some mandatory fields. The stroked one are the mandatory fields but random values for users. For example, user A : the security policy can be xyz1 and security profile xyz2. For user B : the security policy can be abc1 and security profile can be abc2. I can get the other details from identitynow attribute and add create account operation. but how I will add these security profile and security policy field for the user in for account create provisioning? these two fieldsncan have any value from the application randomly. they dont have particular mapping for security policy and profile
These are dynamic values per user. Define them in Create Account Provisioning Policy Form, capture them during access request and pass them using $plan in the API body.
Check the similar post Provisioning using Web Service Connector and APIs: How to Add Entitlements with Individual API Calls - #4 by Jose_Perez
