Workaround to allow the oauthrefresher to retrieve the latest oauth token from JupyterHub.
The Jupyter Server Extension that retrieves the user oauth token from JupyterHub (renewed by the Authenticator), assumed that the auth state was visible to the user and it was possible to retrieve it via the API. But this only happens to admins and not to a normal user, thus invalidating our approach. With this change I force the auth state to be visible, even for normal users, while I wait for a clarification with upstream. Ofc others users will only be able to see their tokens and no one else's.
Workaround to allow the oauthrefresher to retrieve the latest oauth token from JupyterHub.
The Jupyter Server Extension that retrieves the user oauth token from JupyterHub (renewed by the Authenticator), assumed that the auth state was visible to the user and it was possible to retrieve it via the API. But this only happens to admins and not to a normal user, thus invalidating our approach. With this change I force the auth state to be visible, even for normal users, while I wait for a clarification with upstream. Ofc others users will only be able to see their tokens and no one else's.
Related to swan-cern/jupyter-extensions#27