-
Notifications
You must be signed in to change notification settings - Fork 405
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
WEB_AUTH on REAUTH breaks connection #282
Comments
@lstipakov do you have an hint for me to debug this issue? |
Sorry for the delay. This looks like a bug in OpenVPN Connect, not in core library. We have the similar bug in Windows client and provided a workaround until it is fixed. Since this is not a core library issue, I am closing this ticket and suggest you to contact OpenVPN Support - unfortunately they're not monitoring GitHub. |
Hi @lstipakov the OpenVPN Support does not provide an option create an request for OpenVPN Connect. Seems like an unresolvable deadlock here. |
|
Thanks @lstipakov, however I stuck here It seems like running OpenVPN connect against OpenVPN 2 server is not a supported scenario. Thanks for you help! |
hey @jkroepke - check again, I've discussed this with people in OpenVPN Inc. and they've added community edition to that support form. So you can submit your issue now. It seems quite likely like a bug in OpenVPN Connect. And I can tell you that OpenVPN Inc. definitely do wants to get those bug reports. OpenVPN Connect is created and maintained by OpenVPN Inc. and is free and works with Access Server, CloudConnexa, and open source community edition. However, as you can imagine, since OpenVPN Inc. sells the products Access Server and CloudConnexa, those paying customers get support connecting OpenVPN Connect and open source clients to those paid server products. But the reverse, connecting OpenVPN Connect to an open source server, that is lower on the priority in terms of support because OpenVPN Inc. doesn't get any money from paying customers from that. There is of course the forums.openvpn.net for community support, but this smells like a bug report that the maintainers need to know and looks like best reported to where they want it to be reported - support.openvpn.net. So what I'm saying is, what you can expect is that the bug report for OpenVPN Connect will be taken and reviewed gladly on support.openvpn.net, but if the issue turns out to be in the open source community OpenVPN server configuration, then that's something OpenVPN Inc. probably won't be able to solve for you. But honestly after looking at this, it seems like a bug purely in Connect. |
Hey @novaflash reading your post makes me happy. Did not expect that OpenVPN Inc has some interest for bugs which may not exists if Connect is used against non commerical products. I understand that the priority is low for free users and if there is a solution in 6-9 months, I'm more than happy. Thanks a lot. 👍 |
Hey @novaflash, i have still some issues with support. I may still need assistance here. I choice the new option 'community edition'. |
Probably they just need to check internally about change of procedure in this regard. I'm sure it will be fine, give it some time. |
atm the workaround here is to set in the .ovpn client config and no auth-user-pass-optional in server config.
not the same context, I'm also supplying client certs and authenticating with webauth |
Hi,
I'm running OpenVPN Connect v3 for Mac against a private OpenVPN 2 server.
The OpenVPN 2 server has deferred auth enabled which returns a WEB_AUTH to the client.
While the initial authentication works fine, there are some issues on REAUTH.
The OpenVPN 3 client opens the browser and the OIDC flow succeed successfully.
However, the client stuck here
even after closing the browser tab.
In the server log, I can see that there is no
PUSH: Received control message: 'PUSH_REQUEST'
Server logs
Client logs
The text was updated successfully, but these errors were encountered: