Notifications
Clear all
Topic starter
I'm attempting to retrieve some data from my bank, and they provide an OAuth2 API.
However, they mandate custom headers for every request, as well as during the OAuth2 setup.
I'm unable to finalize the OAuth2 setup because it returns an 'unknown client id' error, which I suspect is due to not setting the client ID header.
I haven't found a method to configure such headers within the OAuth2 API credentials setup. Is there a way to accomplish this? If not, could you suggest a workaround?
Here's what their documentation states:
Before You Start
All AIS Service calls require the following headers:
X-Request-ID: a client generated guid to uniquely identify each call
X-IBM-Client-Id: myapp001.ClientId
Posted : 28/11/2020 4:08 pm
Welcome to the community!
Unfortunately, that's not currently possible as it hasn't been a requirement for any services integrated with callin.io to date. You can submit a feature request for us to consider adding it in the future.
The only workaround for now would be to implement the OAuth2 logic manually using HTTP Request Nodes.
Posted : 29/11/2020 11:08 am
Topic starter
Thank you for the greeting, it's a pleasure to meet you!
Understood, I will experiment with a few potential solutions. If I discover anything beneficial for the community, I'll be sure to share.
Keep up the excellent work!
Posted : 29/11/2020 7:03 pm
How did you get around it?
Posted : 18/02/2021 9:52 am
Topic starter
Not yet, I haven't had the chance to work on it (I know, it's been a while). Implementing OAuth2 manually is quite involved. I was thinking about submitting a patch to add support for it. I've opened a related feature request. Actually, there are two, because banks also require mTLS (mutual TLS), which means you need to present a specific client certificate during the TLS connection establishment after the server certificate verification. These feature requests begin with "Banking: "…
Posted : 18/02/2021 11:00 am