Share
Report
32Hello all,
I've run into two issues lately with API authentication with a Custom Connector and it has to do with creating the API key at runtime.
1. The First API requires the first call to be made to a non authenticated website with headers of username/password to get the API password responded to you.
2. Is a little simpler and just needs the secret Base64 encoded with the epoc timestamp added at the end. Like below
signature = base64(HMAC-SHA256(Access Key,HTTP VERB + TIMESTAMP (in epoch milliseconds) + POST/PUT DATA (if any) + RESOURCE PATH) )
Authorization: LMv1 AccessId:Signature:Timestamp
I have found a work around I really don't like which is making the Rest call to get the API key in clear text in the flow, then taking that output. Adding it to a header that a Policy that renames to Authentication. This seems really clunky and I'm wondering if there is a way to simplify this. At the end of the day its an API call however, I need to dynamically assign that API key either at runtime. Or with code that could change it at runtime like in the second example.
Thanks
All responses (
Answers (
