WebService-Connector - Create Account Operation is not triggering

WebService-Connector - Create Account Operation is not Triggering

Hi Team,
I am trying to do Create Account Operation for my Webservice Connector, which targets Okta. When I created a new Identity in SailPoint, this operation is not triggering.

When I am executing the same values in postman it is working, but it is not working in Sailpoint. Test connection and Aggregation are working.

Below is the screenshot of the body Context from Postman and SailPoint Configuration.
SailPoint:

Body:

{
    "profile":
		{
			"firstName": "$plan.firstName$",
			"lastName": "$plan.lastName$",
			"email": "$plan.email$",
			"login": "$plan.email$",
			"displayName": "$plan.empid$",
			"countryCode": "$plan.country$",
			"city": "$plan.city$",
			"state": "$plan.state$",
			"employeeNumber": "$plan.uid$",
			"organization": "$plan.organization$",
			"zipCode": "$plan.pincode$",
			"nickName": "$plan.identificationNumber$",
			"title": "$plan.manager$"
		},
    "credentials": 
	{
        "password": 
		{
            "value": "Sailpoint@2023"
        }
    }
}

Postman:

Any suggestions.

Have you added the Content-type : application/json to the header in your Create Account configuration?
And, are all the attributes used inside the json requestBody ("$plan.attribute$") of the operation available in the Account Schema / Create Account Profile?

Hi @iamnithesh,

Yes, I have added the Content-Type and also have same attributes in both Create Account operation, Create Account Schema, Create Account profile.

I would suggest enabling debug logs on Web Services so that you can see what is being sent by the connector.

@swapnasarit If you create a new identity in SailPoint, have you configured the LCS or role to trigger the grant of an Okta entitlement?. Did you try manually requesting an entitlement that triggers create action?

@anneragh I tried in both ways, to create account based on the lifecycle state as well as from request center. For both the process, I am getting 403 error but the same API, header, body content works with Postman.

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