External Workflows can't generate oauth credentials when description contains new lines

Feedback Bugs
, ,
1

Hi @colin_mckibben,

I stumbled upon a bug where you can’t generate a token to execute a workflow from within the workflow itself if this workflow has a description containing enters \n in them.

I had to investigate the issue, detect the problem, remove the description, generate the token, add the description back.

I then saw that this issue was already reported by @WyssAJ01 and you have created a SailPoint Bug Ticket over 250+ days ago. However, the issue is not fixed yet.

I think, ideally, we should be surprised by such a big resolution time.

Could you please check if this ticket has been picked up already? See PLTWRKFLW-3915

Kind regards,
Angelo

1 Like
2

This is classified as a minor bug and therefor low priority compared to other features/bugs being worked on. The workaround is to not use newlines.

2 Likes
3

Thank you for your response @colin_mckibben,
Is there an SLA for minor bugs? Or is there an ETA for this one? Another 250 days, 3 years?

Even though there is a workaround here, I can imagine other customers not being aware of this getting stuck on this point. And it is not that straightforward to see what is the cause of the issue, which can cause development delays, especially in combination with all the other bugs in workflows that are considered low priority. I understand this alone is a small one. But this is not the only minor bug in workflows that is pending for fixing.

Seeing the amount of bugs or lack of functionality I encounter while trying to use workflows and the response time I see on the bugs that have been reported, I have to admit it does create a growing distaste for using workflows at all or reporting the bugs at all, considering the amount of time before they get fixed.

And for this one, the root cause is clear. Workflows can have descriptions with newlines, but if an end user wants to create client credentials for executing this workflow, the system tries to use this workflows description as input for the API token. But the API token does not support newlines in the description.

So the quick solution would be to use the same string-purify functionality SailPoint uses when a role description is being displayed in several parts of the UI. It strips all newlines and takes what is left. This can also be done to tackle this issue.

Kind regards,
Angelo

4

It will be worked on, but no estimate is available.

1 Like