API Key Authentication in REST Call
-
Christopher Steinbach1 year ago #40663
Hi Simplifier,
how can I use API key authentication in a REST connector call? The API key should be send as an custom http header. The key is different depending on the simplifier environment.
I can’t find a dedicated login method for this kind of authentication.
I’m aware that I could set an http header inside a call definition but:
- …then the key is exposed in clear text to others.
- …the API key is endpoint specific and each environment has it own key.
Is there maybe a workaround to use API key authentication in Simplifier? I thought maybe there are some hidden variables to access in a REST connector call.
Thank you in advance.
Andreas DallnerHas successfully completed the online course IntroductionHas successfully completed the online course Intermediate (200)Has successfully completed the online course Advanced (300)Has successfully completed the online course Basics (100)Has successfully completed the online course Advanced (310)Has successfully completed the online course Advanced (320)Has successfully completed the Intermediate CertificationHas successfully completed the Advanced Certification1 year ago #40671::Hi Christoph,
if your key is the only secret or auth method, than I would suggest to configure a token login methon in advanced mode -> Here you can set the source to “Provided source” and your API key as token and with the Target “Header Parameter” the required header parameter name.
This login method can now be configured on each endpoint. When using different API keys for each endpoint just create a login method for each API key.
If you require more than one secret (e.g. client-secret and password) or if the API key has to be part of body or query parameters, we suggest to create a Simplifier User as API User, add the secrets as user attributes. Than you need to fetch the data from the API User’s attributes and set them as payload for the connector within a serverside business object.
Kind regards,
Andreas
You must be logged in to reply to this topic.