-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
No information returned from Google oAuth #201
Comments
After reading part of the source code, it seems that there is no way to tell openvpn any information about the user that has just been authenticated...
the only answer given to openvpn is the original openvpn username (which may be empty) Am I wrong? Is there any way to give openvpn the identity of the oAuth-authenticated user? |
That is strange, it looks different at my side (I'm using Google Workspace as well):
The ip fields are new (merged yesterday, but not released yet), But I'm also missing the The problem cloud be that you are configure too much. The recommend setting is
and the auto-discovery should do the rest
Correct. The request you are looking for the this (please leave a vote on first post): There was a recent discussion in yesterdays, here is a summerize: Using Enterprise-like feature (like WebAuth with SSO) together with native OpenVPN features is combination, which is currently not in Scope of OpenVPN itself. While the feature request is valid, there is not enough attraction to implement it. The core maintainers says, I should re-implement every feature in openvpn-auth-oauth2 the same way that other enterprise implementation do it. |
Not even that. |
you are right: since I configured that before the google provider existed, I didn't change anything ... I reconfigured and tested again :
it works now, I just have this 118sthg id sent to openvpn, which is not transmitted to client-connect (which confirms your last message above) so the feature request remains :) thanks for the references to openvpn, I'll read that... |
I would like to lose this in favor of #139. The issue is around report the username back to OpenVPN. If the username is in OpenVPN context, it may can used in client-connect scripts than. |
Yes, this request is a duplicate of #139. I close it now unless you have another idea. Thanks! |
Current Behavior
I'm using the google provider and it works fine with the configuration below
That said, I need to know the identity of our connected user to know which IP address to give him/her later in the openvpn, via a client-connect script.
openvpn-auth-oauth2 is logging this when the user is logged-in :
I see that there is no username or subject returned by the oAuth session... Is it normal?
I expect to get some information from google regarding the logged-in user but I have none...
Expected Behavior
I expect openvpn-auth-oauth2 to get an email or name from the oAuth process, that can be then processed by openvpn (example via a client-connect script).
If it's clearly non-standard, feel free to replace this bug to be a feature request <3 and let's talk about it.
Steps To Reproduce
No response
Environment
openvpn-auth-oauth2 logs
openvpn server logs
The "Login not found" is from a client-connect script, that receive a complete environment, but no username or email in this environment :/
Anything else?
my openvpn-oauth config is as such :
The text was updated successfully, but these errors were encountered: