Source import through beta/sp-config/import - Missing ID bug

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello everyone,
I think I hit a bug over the beta/sp-config/import API.
While trying to upload a valid SOURCE template following the documentation, it seems like that missing the ‘.objects[0].self.id’ from JSON will produce an error.
Actually, the job will be submitted, it will FAIL with error:

{
  "completed": null,
  "created": "<REDACTED>",
  "description": null,
  "expiration": "<REDACTED>",
  "jobId": "<REDACTED>",
  "message": "java.lang.NullPointerException",
  "modified": "<REDACTED>",
  "status": "FAILED",
  "type": "IMPORT"
}

And by downloading the report it will state:

{
  "detailCode": "400.1.3 Illegal value",
  "messages": [
    {
      "locale": "en-US",
      "localeOrigin": "DEFAULT",
      "text": "Failed to download file for jobId <REDACTED> and status FAILED"
    }
  ],
  "trackingId": "<REDACTED>"
}

This is kinda tricky, because the ID should be automatically given by the tenant itself, even if the documentation shows that an ID should be present.

It gets even odd though: even when getting the exception, the SOURCE gets imported eventually into the tenant.
More on this: if you type a random ID into the JSON, it will now produce the exception, but that ID won’t be honored! By requesting to the tenant the ID of the imported source, it will return a new (random) ID.

I think this is definitely a bug in this API.

Let me know yours thoughts about it.

2

Thank you for bringing this to our attention. I have created an engineering ticket to have this looked at. I’ll keep this topic updated with the progress.

3

@szucchi Please try now. Engineering has released a fix.