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
I've encountered this problem with the MVD but it's related to the DataDashboard.
Inside the MVD I've introduced the HttpProxy transfer and inside my Dashboard I receive the token and the endpoint to be used to make the get call to receive the data.
But when I make the call I've noticed that the token is changed inside the lazyUpdate, for this reason the call responds with 403 Forbidden error. This is due to the fact that the token of the HttpProxy isn't a Bearer token and so the lazyUpdate change it to a Bearer token.
Is it possible that the problem is related to the HttpInterceptors?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've encountered this problem with the MVD but it's related to the DataDashboard.
Inside the MVD I've introduced the HttpProxy transfer and inside my Dashboard I receive the token and the endpoint to be used to make the get call to receive the data.
But when I make the call I've noticed that the token is changed inside the lazyUpdate, for this reason the call responds with 403 Forbidden error. This is due to the fact that the token of the HttpProxy isn't a Bearer token and so the lazyUpdate change it to a Bearer token.
Is it possible that the problem is related to the HttpInterceptors?
Beta Was this translation helpful? Give feedback.
All reactions