During the deployment of the srv instance we get an error. The log tells:
:npm ERR! Invalid package name "uuid 2": name can only contain URL-friendly characters
This error is new.
The package-lock.json shows for "@sap/cds-foss" a dependeny to "...
We use the CAP for developing locally and then deploying to SAP Cloud Platform. In the past there was no problem for the service instance to get the right handler files. Since a newer release of cap , we had to implement the @impl tag in cat.service....
If the data access takes place via an APP router -as it recommended for XSUAA authentication- the transfered user will be always "anonymous" :
srv.before('READ', 'Partner', request => {
var user = request.user.id; // <<< always "anonymous...
Hi Johannes,there was a X-mas wonder It runs now. I'm not really sure.But maybe I had an "npm update" issue inside the srv-folder, which invokes the inconsistence .ThanksStefan
It seems to be 2.2.0"@sap/cds-foss": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/@sap/cds-foss/-/cds-foss-2.2.0.tgz",
"integrity": "sha512-tOudlvY+YQ7cc5W2srUPEkpoz5syJHw5oezkRWd2PF9TMuIXXEFUTAsRP...
I got the solution. If you call the service via AppRouter you will have to add an additional header parameter, called x-approuter-authorization, filled with the same information as parameter Authorization, which means: "Bearer "+Token .
Nearby one year ago and I'm facing the same problem. As Benjamin told:JWT token is not delivered to or recognized from the srv-Module because when I call the oData Service (srv-Module) via AppRouter, I am routed to the login page and after successful...
