Flow Action, REST step, Issue adding Credential
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2023 04:04 AM
Hi all,
I'm trying to create a flow action to make an API call.
I have created a credential record (API Key), a connection record, and an alias.
I'm using the connection alias in my REST step, and I'm using the data pill to add the credential value to the header:
When I test the step, I get an error: code: 401 - Invalid username/password combo.
If I paste the API token directly into the value for the token header (in lieu of the Credential value data pill) the API call is made successfully.
And here's the thing: when I look at the Request headers in the outbound HTTP log, I can see that ServiceNow is adding the text 'authorization=' in front of the actual API key, and it's leaving the 'token' header without a value:
So I can make this work, by simply pasting the API key directly into the value for the token header, but I would like to avoid having to do this, and would prefer to follow best practice using the connection alias.
Any thoughts on this issue?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 05:52 AM
Fun fact. I originally used a certain word in my previous post, and I got this message:
But, apparently I am allowed to use the word ecstacy 😉
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 03:29 AM
Hi Jamsta,
Do you use this method in scoped app or global?