CI URL Authentication using HTTP Header structure

[rrmalgi]

Hi,

We have an interesting scenario where a client does not support basic auth configuration when calling CI URL but supports only passing details in HTTP Header structure. For <API Key> : <API Value> being passed in the Header structure to POST a message to CI URL.

I have only used client id/secret for basic authentication and certificate based authentication. This kind of requirement is new to me.

Request the community to help if you have solved such requirements (without the use of API-M)

Best Regards

[Merina1]

Hi,

Is there any reason why API-M is not being considered. We had similar scenario and the implementation was simple .

Eg. External system --> API-M --> CI--> Target System

Regards,

Merina Acharya

[MortenWittrock]

Hi

Basically you can't implement that with a sender channel in SAP Cloud Integration. The channel not authenticating and you then performing custom authentication inside the integration flow is not an option. If basic authentication, OAuth 2.0 (client credentials) or client certificates won't work, you need to proxy the endpoint somehow. SAP API Management is the obvious choice for this.

Regards,

Morten

[rrmalgi]

Thanks for confirming my understanding 7a519509aed84a2c9e6f627841825b5a . In the meantime I realised we can pass base64 encoded password in Headers using postman with Header Key "Authorization" and Header Value "Basic base64encodedPassword"

[MortenWittrock]

Hi rrmalgi

Well, what you are describing there is Basic Authentication, which is of course supported.

Regards,

Morten