ISC Workflows external trigger URL keeps growing

Feedback Bugs
,
1

Hi all, :slight_smile:

Let’s start with a workflow with an easy quick external trigger that immediately ends (just for simplicity purposes, the issue also exists with complex workflows).

image
image1124×649 63.7 KB

We check the workflow json with /beta/workflows and we see at the bottom of this workflow:

"trigger": {
  "type": "",
  "attributes": {}
}

We now add a description to the trigger in the UI, hit save and check the JSON again:

image
image372×454 7.48 KB

"trigger": {
    "type": "EXTERNAL",
    "attributes": {
        "description": "test",
        "url": "https://eu-partner18.api.identitynow.comundefined"
    }
}

Note the strange url. Let’s change the description now and check again:

"trigger": {
   "type": "EXTERNAL",
      "attributes": {
      "description": "test 2",
      "url": "https://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comundefined"
   }
}

Notice how the url has gotten bigger. Let’s do it some more times:

"trigger": {
   "type": "EXTERNAL",
   "attributes": {
      "description": "test 10",
      "url": "https://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.comundefined"
   }
}

Let’s now generate the client ID and secret belonging to the workflow

image
image350×660 14.1 KB

"trigger": {
   "type": "EXTERNAL",
   "attributes": {
      "clientId": "15bb4639-c6bc-47cf-90c3-ff6726d60575",
      "description": "test 10",
      "url": "/beta/workflows/execute/external/2ae43a9d-105a-4f5b-a89e-cf17199bdba1"
   }
}

Now the URL is somewhat back to normal and it has become a relative URL. Let’s change the description one more time.

"trigger": {
   "type": "EXTERNAL",
   "attributes": {
      "clientId": "15bb4639-c6bc-47cf-90c3-ff6726d60575",
      "description": "test 11",
      "url": "https://eu-partner18.api.identitynow.com/beta/workflows/execute/external/2ae43a9d-105a-4f5b-a89e-cf17199bdba1"
   }
}

And one last time:

"trigger": {
   "type": "EXTERNAL",
   "attributes": {
      "clientId": "15bb4639-c6bc-47cf-90c3-ff6726d60575",
      "description": "test 12",
      "url": "https://eu-partner18.api.identitynow.comhttps://eu-partner18.api.identitynow.com/beta/workflows/execute/external/2ae43a9d-105a-4f5b-a89e-cf17199bdba1"
   }
}
1 Like
2

The reported issue has been identified as a defect and a fix for this will be tracked via PLTWRKFLW-3010.

2 Likes
3

The growing part of it is fixed, but the other weird inconsistencies occurring are still happening. I think information might have gotten lost in the chain of communication between SailPoint Support, the internal ticket where we as outsiders can’t see the content and the engineering team.

It still is different before and after adding a description. It still mentions the odd string ...identitynow.comundefined and there is also a difference between adding client credentials and then updating the description and adding client credentials and then not updating the description.

1 Like