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 topic.
I am working on creating a source using "webservices SaaS connector’. Before trying in ISC, i tried it in Postman and i am able to perform the basic operations of create account. In ISC, i created the custom HTTP operations. Test connection is working fine. Get Entitlements, i am able to get the entitlements. Now i am trying to create the account. I configured the Account schema, i added the create account profile, added the HTTP operations for the create account.
But when i try to create the account through access request, it is failing with the below error,
[“sailpoint.connector.ConnectorException: HTTP Error 400 when communicating with URI https://stg01-apsoutheast2-sp-connect.accessiq.sailpoint.com/connector-instances/d0d27823-8754-427e-9270-fa1fcd37e0b1/commands : {\“detailCode\”:\“Bad Request\”,\“trackingId\”:\“4b382b8e41ec4be18a36045e7c754920\”,\“messages\”:[{\“locale\”:\“en-US\”,\“localeOrigin\”:\“DEFAULT\”,\“text\”:\” Schema validation error in path: [{allOf all_of_item_mismatch Value does not match the allOf schema at index {indexs} map[indexs:0]} { {Valid:false EvaluationPath:/properties/attribute SchemaLocation:#/properties/attribute InstanceLocation:/attribute Annotations:map[] Errors:map[type:Value is null but should be string] Details:[]} map[]}]\“}]}”]
Instead of passing dynamic values, i hardcoded the values in the Raw json body which worked in Postman, still it is failing with the above error.
Errors:map[type:Value is null but should be string]
The error says that a value is null, so it could be that it is failing at the validation when creating the request.
Perhaps you could in a first step, try hardcoding the values in the JSON to confirm that the request works when sending via SailPoint. In a second step, replace each value with the variable way using the $plan.variable$ one by one. You should then see which variable isn’t resolving to a value, and then go from there.
Hope this helps! I’m not the biggest pro with the WebServices SaaS
@othornewill Thanks for your response. As i mentioned above, i tried hardcoding all the values in the create account Raw json. Still it failed with that error.
This 400 comes from ISC before your HTTP operation runs. The URL in the error is the connector command endpoint (/connector-instances/.../commands), and “Schema validation error” means ISC rejected the command payload it built. Your request body never reaches the target. That’s why hardcoding the values (Oliver’s suggestion) and fixing the givenName typo Naveen spotted didn’t change the result. Jay Khatri reported the same error in this thread, and his request never reached the target either.
InstanceLocation:/attribute with Value is null but should be string means a top-level string field called attribute is null in that payload. Your body has no such field, so ISC fills it from the source configuration. In a provisioning plan, attribute names the account attribute an entitlement belongs to. You trigger the create with an entitlement access request, so I suspect the requested entitlement isn’t linked to an account attribute.
I would check the account schema first. The attribute that holds the entitlements should be marked Entitlement and Multi-valued, with an entitlement type that matches your entitlement schema (Managing Source Account Schemas). Then call get an entitlement on the entitlement you requested and look at its attribute field. If it’s null, the entitlements were aggregated before the link existed. In that case, fix the schema, run entitlement aggregation again and submit a new request.
If both look correct, please share the account schema and the entitlement JSON with IDs redacted, and also please answer Jeremy’s question about Single Account Aggregation.
Thanks for testing. Since hardcoding the body gives the same error, the body is not the problem. The 400 comes from schema validation of the command payload that ISC builds before it calls your endpoint, and the attribute field in that payload is null. Please check the following:
Create Account provisioning policy. Run GET /v3/sources/{sourceId}/provisioning-policies. Look at every field under fields. Any entry with an empty or missing name can produce a null attribute. Delete it and re-add it from the dropdown.
Account schema. Run GET /v3/sources/{sourceId}/schemas. Confirm identityAttribute and displayAttribute are set to real attribute names, and that no attribute has an empty name.
Hello Vidya Sagar. Naveen’s checks are worth adding. At this point there are two good places to inspect before changing the HTTP operation again, and I would treat both as configuration validation rather than a confirmed cause until the output is in.
I would start with Pratyush’s check on the exact entitlement being requested. If its attribute is null, that matches the validation error very closely, and I would fix the Account Schema to entitlement-type (schemaObjectType) relationship and run entitlement aggregation again.
If the entitlement attribute is already populated correctly, then Naveen’s provisioning-policy check is the right next step. GET /v3/sources/{sourceId}/provisioning-policies shows the CREATE policy and its fields, and each field should have a valid name matching an account attribute. It is also worth confirming, as Naveen said, that the Account Schema identityAttribute and displayAttribute reference real attributes and that no schema attribute has an empty name (GET /v3/sources/{sourceId}/schemas).
So the discriminator is:
entitlement attribute null → fix the entitlement/schema linkage and re-aggregate
entitlement attribute valid → inspect the CREATE provisioning-policy field names, then the generated plan
I would wait for the output of those checks before changing the Create Account HTTP operation again.
@punna0001@naveenkumar3@Pratyush27 Thanks for the response. I understood the same after my multiple tries, It is erroring out before the HTTP call itslef. I am adding the account, group schema and also the create account policy.
Instead of the generic error, if the ISC mentions the attribute name it has issues with, i think debugging and resolving is much easy.
Hello Vidya Sagar. Thanks for sharing the config. I went through the Account Schema, Group Schema, and Create Account policy, and they look structurally fine. The CREATE fields have valid names, externalId / userName are set correctly, and groups is already configured as a multi-valued entitlement linked to the group schema. Since Single Account Aggregation also works, I would keep Get Object aside for this error.
The next thing I would check is the actual group entitlement in the Access Profile:
If attribute is null or empty, that would line up very closely with the error. I would re-run the group/entitlement aggregation and confirm it comes back as:
If attribute already shows groups and sourceSchemaObjectType is correct, then I would move to the generated provisioning plan or connector log and check which object is actually carrying the null attribute.
I didn’t create any access profile. I was trying by submitting an access request for the entitlement itself. Below is the search result on the entitilement,
The entitlement has "attribute": null, so the provisioning plan contains an item with no attribute name. The groups attribute in your account schema is not marked Managed (isManaged: false), so entitlements are never tied to it. Tick Managed on groups, save, run entitlement aggregation again, confirm the entitlement now shows "attribute": "groups", then retry the access request.
You will need an Add Entitlement operation to actually add the user to the group.
@kompala Naveen’s fix matches your config. In the account schema you posted, groups is linked to the group schema but has "isManaged": false. The Connector Specification File docs define managed as “Whether the entitlements are manageable through SHF (true) or read-only (false)”. A read-only entitlement fits the "attribute": null you are seeing.
If attribute is still null after you set Managed and aggregate entitlements again, also add this to the same groups attribute:
"schemaObjectType": "group"
Right now groups points to the group schema only through the schema reference. In the thread Harish linked, the cproblem was still the same until schemaObjectType was added (post #20).
On where to get the logs, SailPoint added a log download for SaaS connectors last week (announcement). It is under Admin > Sources > your source > Additional Settings > Administrator Settings and covers about the last 24 hours. You can turn on debug logging there and download again. It reached sandbox tenants on September 21 and reaches production on September 30. If not, you can reach out to sailpoint support.
Hello Vidya Sagar. I agree with @naveenkumar3 & @Pratyush27 on this one. Your entitlement’s "attribute": null now gives us something concrete to work with.
I would update the groups account attribute so it is Managed, and also confirm it has schemaObjectType = "group", not only the connector-schema reference. Then run Group Aggregation again and check the same entitlement. The result we want to see is:
I would check schemaObjectType explicitly is that in the similar case earlier, the schema reference alone was not enough, and adding schemaObjectType was what finally populated the entitlement relationship.
Also, since this is a direct entitlement request, make sure you have an Add Entitlement operation configured, unless you are intentionally using Create Account With “Ent” Request. I would test those changes first and see whether attribute gets populated.
Thanks for the response. I need help with 2 things,
How to mark the attribute in account schema as ‘Managed’. There is no option in the UI. Should i update it through API call ?
I enabled debug mode in the source. I tested multiple times. When i download the logs for the last hour, file inside the .gz is 0 bytes. There is no entry in the connector logs.
Hello Vidya Sagar. On the first point, I would not update isManaged through the API yet. I checked the current public Source Schema API, and isManaged is not documented as a writable account-schema field. The API does document isEntitlement, isGroup, isMulti, and the reference to the group schema, and those already look correct in the schema you shared. So I would first run Group Aggregation again and check the same entitlement. If it changes from:
"attribute": null
to:
"attribute": "groups"
then retry the access request.
If it still stays null, I would stop changing the schema through undocumented API fields and raise it with SailPoint Support with the Account Schema and entitlement JSON. I would specifically ask how managed is expected to be enabled for a Web Services SaaS entitlement when the UI does not expose it.
For the logs, the 0-byte file could fit what we are seeing, since this request is failing before the Create Account HTTP operation runs. One simple test: leave debug enabled, run Single Account Aggregation again since you already know that reaches the connector, then download the last-hour logs.
If that successful operation appears, the empty log for this failed request makes sense.
If the file is still 0 bytes even after a successful connector operation, I would raise the logging issue with Support too.
The new SaaS Connector Log Download provides roughly 24 hours of connector-specific logs and supports debug logging. Production rollout is September 30, so if this is a Production tenant, that timing may also be relevant.
I would try those two checks first: Group Aggregation and the successful Single Account Aggregation log test.