Improve default oauth interceptor

[simonmulser]

In a project we have the problem that after the redirection the access_token is not available. Hence, the first requests are sent without the token even we configured the interceptor with send_access_token. In the projekt we are using a custom interceptor similar to improved interceptor in the PR, where we wait for the token to be loaded from the OAuthService. I wanted to contribute this change back.

Let me know if this change makes sense for you.

[jeroenheijmans]

Interesting PR! Have not had time to test it yet, but looks like a good idea. Only thing I conceptually I'm on the fence about is whether you want this behavior always, or possibly as an opt in for users. Some might prefer their own services and whatnot to handle this...

Has a (thin) relation to #414

[simonmulser]

ok. let me know when and what I should adopt. could also provide some unit tests.

[manfredsteyer]

Thanks for this PR. I'm not sure about it. Does it postpone the request every time for 1 sec?

[simonmulser]

nope.
if the token is present the request is sent immediatley.
if the token is not present the code waits 1 sec for the token received event.
if the token arrives in that time window the request is sent immediatley.
if not the request is sent without header.

[manfredsteyer]

thx!

[manfredsteyer]

This would be a nice PR: adding a flag that makes the interceptor to refresh the token when it was expired

[simonmulser]

@manfredsteyer you want to make this behavior configurable with a flag?