Say I have 10 HTTP Action steps that call up IDN v2024 APIs in each workflow, and that we have 20 workflows. What’s the best way to manage / reference / update these client IDs and client secrets in the workflows? Or even auto rotate the secrets?
This is currently such an overhead for workflows to ‘call itself’ for various actions. Maybe I’m missing something I should know about?
This also creates issue for us that we either have to toggle the workflow offline to modify it, or create a duplicate of the workflow, and toggle / flip to the v2 workflow with updated credentials.
@IIQUserOnCompass I don’t think you can least way to update the client secret, only way is to duplicate the workflow and change the secret or go in each WF and change it.
The idea portal is a purgatory of missing features (and / or bad ideas), may or may not come to fruition. Will leave it to the product team.
One would expect (you would think) there’s a mature way of handling self-referencing PATs (or credentials in general), as IDN is so focused on “we can do it with the APIs”. Like, it’s not enough to just have workflows and APIs. e.g. Being able to make cars at the factory to sell is not enough, you need to provide the tooling to maintain the cars. Tools available at dealerships / service centres. The lifecycle of the components and how to manage them is important. That’s a differentiator of what makes a solution a great solution. Imagine if you had to manage all the Amazon warehouse robots (automation component in a warehouse just like workflows and APIs in IDN to provide automation) manually…