- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2020 08:27 AM
I have a working Rest API Action, that communicate with an external tool and get information related to users.
The Connection used in Rest step call is inline.
All connection attributes are passed in Header:
Everything work fine with this configuration.
Now, I need to move the connection attributes from “Inline Connection” to “Use Connection Alias”.
So I created a new Connection and Credentials Alias with the URL and attributes :
Then I changed the type of connection within Flow Designer action to “Use Connection Alias” and I give my new Created Connection Alias, and I removed all attribute from the Header.
But when I test my action I got errors with the following information :
- Error Code : 1
- Error Message : Method failed: (/api/MyAPI) with code: 400
- Response Body : Invalid authentication content.
- Status Code : 400
How do I change my connection in IntegrationHub from Inline to Connection and Credentials Alias?
Or at leat how can I test and debug this connection issue ?
Solved! Go to Solution.
- Labels:
-
Integrations
-
Scripting and Coding
-
Studio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2020 01:29 PM
Hi,
API key still needs to be passed in the header. Having selected 'Use Connection Alias' is the credential api key not available as a pill value in the right hand data pane? If so, you just drag this into the header.
If it does not exist; you could create a new input for the REST action and pull in the api key value from the table it resides.
Let me know if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2020 01:29 PM
Hi,
API key still needs to be passed in the header. Having selected 'Use Connection Alias' is the credential api key not available as a pill value in the right hand data pane? If so, you just drag this into the header.
If it does not exist; you could create a new input for the REST action and pull in the api key value from the table it resides.
Let me know if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2020 12:11 AM
Hello Alamine,
Please mark my response correct if it answered your question. Let me know if I can help more.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2020 07:55 AM
Hi geoff;
Thanks a lot, I understand better now. Yes I have the attributes as a pill values, I ll use them.
Do you think it may be a security issue to send the api key in the header of API ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2020 09:00 AM
Hi Alamine,
I'm no expert when it comes to your security question so I wont attempt to answer it. Please do mark my original reply to your answer as correct and you can also open a new question on the community with regards to your security question 🙂
Geoff