the-littlest-jupyterhub
the-littlest-jupyterhub copied to clipboard
jupyterhub
NativeAuthenticator: Change password / Authorize links missing in top navigation bar at /hub/home UI
Proposed change
End points such as /hub/authorize and /hub/change-password don't seem to appear in the UI (I use the Lab UI - possibly "change password" appears in the notebook UI?). It would be very helpful if at least /hub/authorize appeared in the admin section when the Native Authentication module is enabled.
Who would use this feature?
Everyone, but particularly new users and admins.
To clarify, the Change password and Authorize links described in this issue are to be be shown like in the image below are not showing up.
I'm not sure why, perhaps this is a permissions issue for templates installed by nativeauthenticator? I suspect this isn't an issue of https://github.com/jupyterhub/nativeauthenticator itself, but an issue of TLJH integration with nativeauthenticator.
@lambdaTotoro do you know if I can debug this failure by searching for some template installed by nativeauthentictor in some specific folder or similar?
My first intuition would be that this has something to do with the changes introduced in jupyterhub/nativeauthenticator#79 . Since they were introduced, things need a little bit of extra fiddling with the template path. That's written about in the installation section of our docs, but I don't know if that made it over to tljh.
@lambdaTotoro ah! No I think that is merged after this has been observed in version 0.0.7 I think, but would things just work if installing 1.0.5 at this point perhaps?
If using 1.0.5, do we also need to configure something like this?
import os
import nativeauthenticator
c.JupyterHub.template_paths = [f"{os.path.dirname(nativeauthenticator.__file__)}/templates/"]
I answered this myself by reading the docs, yes we have to do that: https://native-authenticator.readthedocs.io/en/latest/quickstart.html#installation
I think that'd be worth a shot. Is there a way you could try that and see if it works?
From my POV this is still an issue with 1.0 (we started with the release before).
