Detailed failure information from "sail spconfig import"?

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

I am attempting to import an sp-config object that’s stored in a local JSON file. I am able to run the command (via powershell) normally, and get back a response like this:

PS .../idn-test> Import-BetaSpConfig -Data /path/to/Rule.json

jobId      : 4e142b24-a20e-48b7-80e6-50ee53717cf0
status     : NOT_STARTED
type       : IMPORT
expiration : 8/18/2023 4:52:02 PM
created    : 8/11/2023 4:52:02 PM
modified   : 8/11/2023 4:52:02 PM

I then use the “sail” command to check the job status and get this:

Job Type: IMPORT
Job ID: 4e142b24-a20e-48b7-80e6-50ee53717cf0
Status: FAILED
Expired: 2023-08-18 16:52:02 +0000 UTC
Created: 2023-08-11 16:52:02.224 +0000 UTC
Modified: 2023-08-11 16:52:02.571 +0000 UTC
Completed: 0001-01-01 00:00:00 +0000 UTC

But there’s no information on why it failed or how to get more information. Does more information exist? How can I find out whether my file is invalid?

2

I was able to get detailed error messages by invoking the REST APIs directly in Postman, rather than using the CLI tools. That’s silly.

1 Like
3

Thank @drosenbauer for the update. I think we can also use Job ID and submit it via Postman to get the error message using https://{{idn_OrgID}}.api.identitynow.com/beta/task-status/{task-id}

4

Looks like we have room for improvement in our CLI. @drosenbauer can you submit an issue to the CLI GitHub repo with what you would like to see from the command? We will work on implementing it into the CLI for you so you don’t have to invoke a REST command.

5

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