Skip to content
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

Pass through authentication to Windows hosts #122

Open
andrewyager opened this issue Jun 27, 2024 · 1 comment
Open

Pass through authentication to Windows hosts #122

andrewyager opened this issue Jun 27, 2024 · 1 comment

Comments

@andrewyager
Copy link

I recognise that this is outside the scope of this project, but I'm yet to find a solution that works as I'd like.

I use this project as a front end to Windows RDP servers, and integrate Keycloak for OpenID authentication.

The authentication to the gateway works beautifully, and the username is passed to the RDP Server, but I am yet to find a way to have the authentication (done via OpenID) to persist to the client. Obviously the password is not known at this point, so it can't just be put into the RDP file, and the token doesn't seem to be meaningfully able to be verified by the client.

Are there any suggestions on how to address this? I don't believe we can OpenID auth and then issue a Kerberos token either?

@jothoma1
Copy link

jothoma1 commented Jul 1, 2024

Same scenario for me, if you find a way, let me know please :)

Sorry to ask but, i have a question how do you manage public certificate for RDP ? i have an nginx with public certificate for accessing rdpgw. It works great but all of my RDP servers are internal and i have a warning for "publisher unknown".
I think it's because they present the internal certificate ?
Is there something to do for not having this warning ?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants