Create account Failed for webservice connector

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

Hi everyone,

Create account is getting failed with below error.
[“Exception occurred while performing \u0027Create\u0027 operation on identity \u0027null\u0027: Url: https://CTS-esp.archerirm.us/ws/accesscontrol.asmx, Message: 400 : Bad Request : , HTTP Error Code: 400”]

FYI: we have added all operations.

{“org”: “CTS”, “pod”: “prd01-useast1”, “created”: “2025-06-25T03:11:31.240Z”, “id”: “9e330fd975d1671fabc5da3da0793b557f7788dba5db824ace522a46041ddb08”, “action”: “CreateAccountFailure”, “type”: “PROVISIONING”, “actor”: {“name”: “SYSTEM”}, “target”: {“name”: “YOQ3187”}, “stack”: “wps”, “trackingNumber”: “e5257b8b571844acab4247df30fb64b1”, “attributes”: {“accountUuid”: “null”, “cloudAppName”: “ArcherConnect”, “errors”: “["Exception occurred while performing \u0027Create\u0027 operation on identity \u0027null\u0027: Url: https://CTS-esp.archerirm.us/ws/accesscontrol.asmx, Message: 400 : Bad Request : , HTTP Error Code: 400"]”, “appId”: “fa708bc2c30b44b1ad7f58ec5f3b8434”, “sourceName”: “ArcherConnect”, “interface”: “Identity Refresh”, “attributeValue”: “null”}, “objects”: [“ACCOUNT”], “operation”: “CREATE”, “status”: “FAILED”, “technicalName”: “ACCOUNT_CREATE_FAILED”, “name”: “Create Account Failed”, “synced”: “2025-06-25T03:11:32.066Z”, “_type”: “event”, “_version”: “v2”}
Show syntax highlighted

2

@saikumarS

400 means the BODY is not correct .

  • Check if you are sending the proper body
  • Check If all these attributes in the body are included in Create Account Section

Which Web Service Application is this ? if it is an internal application please share the body that you are sending in Create Account Op.

Thanks

3

Hy Sidharth,

Thanks for the reply.

below is the body that im using it to create the account.

<soap:Envelope xmlns:soap=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:web=“http://archer-tech.com/webservices/”>
soap:Header/
soap:Body
web:CreateUserEx
web:sessionToken$application.accesstoken$</web:sessionToken>
web:firstName$plan.FirstName$</web:firstName>
web:middleName$plan.MiddleName$</web:middleName>
web:lastName$plan.LastName$</web:lastName>
web:companyName$plan.Company$</web:companyName>
web:title$plan.Title$</web:title>
web:securityParameter1</web:securityParameter>
web:address$plan.Address$</web:address>
web:timeZoneEastern Standard Time</web:timeZone>
web:locale</web:locale>
</web:CreateUserEx>
</soap:Body>
</soap:Envelope>

4

@saikumarS

Do we have all these attributes in Create Plan ?

Share the account activity of the same .

5

Below attributes available in the create account .

Middle name has custom transform.

And we observe that ,It is not failing for everyone

web:firstName$plan.FirstName$</web:firstName>
web:middleName$plan.MiddleName$</web:middleName>
web:lastName$plan.LastName$</web:lastName>
web:companyName$plan.Company$</web:companyName>
web:title$plan.Title$</web:title>
web:address$plan.Address$</web:address>

image
image665×489 16.5 KB

6

Okay !!
If this issue isn’t occurring for all identities, please take two examples:

  • One identity where the account was created successfully
  • Another where the account creation failed

Compare the identity attributes for both — particularly those used in the create account mapping and transforms.

Check for any missing values, special characters, or discrepancies that might be causing the failure.

7

I see some difference from create account passed and failed.

image
image1171×466 17 KB

8

The above is expected as this is result of operation .
I want you to compare the Identity Attribute data please .

9

Make sure you’re able to make a successful call via Postman first. 400 Bad Request means something is off with your request.

10

It is success via Postman .

1 Like
11

Then it’s the issue with Identity Attribute data / Transform that is rendered in the body . Please compare the attributes of successful Identity and failed Identity ops.