CAP Node JS - cds.env.features.fetch_csrf per service

[#1]

Hi,

We have a CAP project with a mix of external services. Some require CSRF tokens (SAP backends), some do not require it (non-SAP backends) and some of the latter are not responding well to the "HEAD" requests which are emitted by the SDK to fetch CSRF tokens (fail or cause long delays).

So I need to control this on a per-service level. There is the "cds.env.features.fetch_csrf" flag but it applies across all the services. How can I make it active for a subset of the services? Looking at the sources it seems I might be out of luck here, am I missing something or do I need to patch it and can it be considered for implementation in CAP?

Thanks in advance!

//Carl

[OlenaT · Accepted solution]

Hi onnheimc ,

As I replied in your other question:

We are introducing two new configuration options: csrf: true/false and csrfInBatch: true/false which will allow you to configure csrf token handling pro service. Please track our release notes. Global env variable cds.env.features.fetch_csrf will be deprecated.

Regarding your problem with an action call: We have created a task for this, but there is no timeline on it yet. One of our colleagues will get back to you after the task is completed.

Best regards,

Olena

[carlonnheim · Accepted solution]

That is great news olena_ , many thanks!

//Carl