-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authenticating via REST API #4198
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
I'll close this as resolved by my reply in jupyterhub/zero-to-jupyterhub-k8s#2926 |
Hi there @wudstrand 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the http://discourse.jupyter.org/ forum. Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
@consideRatio I am trying to follow your suggested workaround and I am running into some issues. Since I am not running the jupyterhub UI I cannot access the api token page referenced in your link, and without the code from the
|
Related Github Issue |
Hi there @wudstrand 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the http://discourse.jupyter.org/ forum. Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
I ended up using a service to handle api calls and interaction with the |
Bug description
I am trying to use the hubs REST API from a custom UI and wanted to avoid using an API token and instead use the custom keycloak OAuth authenticator I have setup. Currently the authenticator works when using the provided hub UI, but I cannot figure out how to authenticate with it via the REST API. After combing through the documentation, I've only been able to find information on using API keys to authenticate the REST API.
I have added some links to forum posts I thought might be the right direction, but I am still struggling to find an answer.
Expected behavior
If the API supports this functionality add documentation describing the flow of API calls needed to authenticate through the REST API. If the API doesn't support this, add in support on the REST API to utilize the configured authenticators to authenticate.
Actual behavior
Custom authenticator authenticates users correctly when using the provide hub UI, but all requests to the API via postman receive a 4xx error. The API errors are caused because I am not sure how to authenticate via the REST API.
How to reproduce
I am running jupyterhub via kubernetes and helm following the zero-to-jupyterhub guide. I have outlined the steps below to reproduce my environment and see the bug/issue I am seeing.
values-local.yaml
Visit http://localhost:80 and sign-in to see the hub UI authentication work.
Attempt some of the hub API calls to see 400 error.
Your personal set up
OS: mac OS
The text was updated successfully, but these errors were encountered: