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
Uploads are long-running and invokes disparate services. There is a potential chance that token will get refreshed after the invocation of file uploader, but before the individual calls finish. fileUploader(content, jwt,callback)
JWT can be a string or a callback, but Observables won't bind well results back if we have multiple callbacks. (I need to research more here)
Short-term solutions are
in the absence of jwt, either read the token from cookie (but will kill pure node clients)
is to have an event raised against window or a global event emitter, to which the client reacts and change the token on the fly.
The text was updated successfully, but these errors were encountered:
I would expect that the token in the cookie is always the most up-to-date token, so it would be advantageous to always use that value. That is what we're doing in the MA UI.
Uploads are long-running and invokes disparate services. There is a potential chance that token will get refreshed after the invocation of file uploader, but before the individual calls finish.
fileUploader(content, jwt,callback)
JWT can be a string or a callback, but Observables won't bind well results back if we have multiple callbacks. (I need to research more here)
Short-term solutions are
The text was updated successfully, but these errors were encountered: