Hi Dan, This sounds vaguely related to work I've just been doing on the HashAuthenticator, allowing a separate authentication system to be used for admin users. Maybe our code can give you some hints: https://github.com/thedataincubator/jupyterhub-hashauthenticator On Mar 15 2018, at 11:24 am, Dan Davis <[email protected]> wrote: > > Now it is clear - the web application is initialized rather late, and since > the init_handlers method calls > h.extend(self.authenticator.get_handlers(self)), I simply return additional > handlers that way. > > From the structure of the code, it is pretty clear that each "handler" in > that list should be a tuple of pattern and handler, and this is confirmed by > the implementation of jupyterhub.auth.Authenticator. Yep, with this, it's easy to add additional endpoints. Because this runs within the JupyterHub process, you can (ab)use this to display all sorts of interesting information. (We generate a list of login credentials, for example.) Also worth noting, since it took me a while to find this out: These tuples can have a third element, a dictionary of keyword arguments passed to the initialize method of your handler. Hope that helps, Robert
-- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/1521158773.local-3c6e0596-f515-v1.1.5-5834c99f%40getmailspring.com. For more options, visit https://groups.google.com/d/optout.
