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
For people with a self-hosted Nextcloud instance, it would be very convenient to be able to connect to JupyterHub using the already existing users.
The implementation should be quite straightforward, a first version is available in #321.
I believe the only significant difference from existing connectors is that, because Nextcloud is self-hosted, the instance URL should be passed by the user.
If it fits in the project's scope, please give me a green light and I'd be up for submitting a PR with an updated implementation.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
We aren't generally accepting new OAuthenticator subclasses in this repo. GenericOAuthenticator should work with just about any oauth provider via configuration. If you'd like to add the configuration required to use GenericOAuthenticator to the documentation, that would be very welcome!
Proposed feature
For people with a self-hosted Nextcloud instance, it would be very convenient to be able to connect to JupyterHub using the already existing users.
The implementation should be quite straightforward, a first version is available in #321.
I believe the only significant difference from existing connectors is that, because Nextcloud is self-hosted, the instance URL should be passed by the user.
If it fits in the project's scope, please give me a green light and I'd be up for submitting a PR with an updated implementation.
The text was updated successfully, but these errors were encountered: