on 08-09-2022 3:07 PM
Partner solutions interfacing with SAP LoB cloud applications need to identify itself by submitting an AIR identifier (Application Interface Register) to a custom header parameter with the name 'Application-Interface-Key'.
How do we set the AIR header when using an external service via `cds.connect`?
I've tried to use the headers properties i.c.w. a destination, but in my test it seems that the requests send to the destination are not including that header:
"cds": {
"requires": {
"uaa": {
"kind": "xsuaa"
},
"FoundationPlatformPLT": {
"kind": "odata-v2",
"model": "srv/external/FoundationPlatformPLT",
"[production]": {
"credentials": {
"destination": "sf-end-user",
"headers": {
"Application-Interface-Key": "xxxx"
},
"path": "/odata/v2",
"requestTimeout": 1000000
}
}
}
}
}
Improvement Request to be able to allow this configuration via destination service: https://influence.sap.com/sap/ino/#/idea/289204
Based on the SAP Cloud SDK documentation Additional Headers and Query Parameters on Destinations this can be solved with the Additional Property:
URL.headers.Application-Interface-Key
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.