We are implementing as S/4 HANA CLOUD APIs, performing initial POSTMAN and SOAPUi tests, for external construction purposes with external applications.
All GET processes work perfectly in the case of POST although we have problems with the CSRF token that was lost in the API call, where we made a first call to fetch the token and a call to execute the POST, which this time time ago with Error 403 Forbidden. This error does not occur via POSTMAN where the whole situation occurs without any problem. However great the chance of being different and unusable, the S / 4 HANA CLOUD is not allowed to change the validity time of the Token and or change the Token by a custom.
The two advertisements of different languages, DotNet and PHP, went the same way. API example that has the behavior: API_SUPPLIERINVOICE_PROCESS_SRV - POST Method - A_SupplierInvoice Today uses a communication system with user authentication and password.
We are not using SAP CLOUD ITEGRATION (SCI) for current integrations.
They look for the same, the newer ones are replaced by the current one for a custom, while the others are more tied to the token itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.