-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
[FEAT] Bypass password authentication for API calls #190
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Also interested on this topic. |
Sounds like something that should be requested to the upstream project, we just package what's released. |
For anyone else coming here, the solution is to send requests from the client with credentials. That way the Specifically in my case, I added
client-side, and
server-side. As j0nnymoe mentioned, this is related to the upstream project, and there are several discussions there regarding this. |
Is this a new feature request?
Wanted change
I have a server running on
https://3000.example.tld
and a client running onhttps://4000.example.tld
When I navigate to
https://3000.example.tld
I am redirected tohttps://3000.example.tld/login
withand after inputting password I can navigate to
https://3000.example.tld/api/endpoint
to get a valid JSON response.However, when the client running on
https://4000.example.tld
tries to request a resource on the server, I simply get 401, because the client has obviously not "logged in" to the server. How is the correct way to solve this?Reason for change
The code-server is exposed to the internet, so I can't simply remove the password authentication. However, the client and server have their own authentication mechanisms, so it wouldn't be necessary with password authentication on the proxy domains.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: