You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first step: Getting a valid token works as expected (if the client_id and the client_secret are correct a token is returned, otherwise it fails to the .catch())
However if the client_Id is not configured in the BM WebDav settings the following error appears:
Error: WebDAV authentication failed. Please (re-)authenticate first by running ´sfcc-ci auth:login´ or ´sfcc-ci client:auth´. No token auto-renewal is performed. If the problem still occurs please check the WebDAV Client Permissions on the instance and ensure your client ID has been granted access to required WebDAV resources.
which comes from: sfcc-ci/lib/ocapi.js:75~ensureValidToken
The problem is that ensureValidToken ONLY logs the error but DOES NOT call the callback with an error (which I can handle in my Promise chain)
The text was updated successfully, but these errors were encountered:
Hello,
I am using the following code to upload a code version within a grunt task:
The first step: Getting a valid token works as expected (if the client_id and the client_secret are correct a token is returned, otherwise it fails to the .catch())
However if the client_Id is not configured in the BM WebDav settings the following error appears:
which comes from:
sfcc-ci/lib/ocapi.js:75~ensureValidToken
The problem is that
ensureValidToken
ONLY logs the error but DOES NOT call the callback with an error (which I can handle in my Promise chain)The text was updated successfully, but these errors were encountered: