Closed andreas-p closed 9 months ago
tbh. I never test this feature together with
username-as-common-name
verify-client-cert none
And its suspicions to me that the common_name is empty on the log side.
However if the common name is empty, the auth should be blocked
I have to investigate the issue, but it will take some time.
Happening with openvpn2.6.3 from Debian Bookworm
I integrated some test and figure out a typo in the config struct, should be fixed with #151
There is an additional in #154
Current Behavior
Using openvpn-auth-oauth2_1.13.5_linux_amd64.deb, I configured openvpn-auth to start with the command line option
--oauth2.validate.common-name preferred_username
.On the server side, I have
When connecting using openvpn3 with username "nobody" (authorizing via Nextcloud), I see
Obviously, cn "nobody" and preferred_username don't match.
Expected Behavior
Deny connection if cn and configured field from oauth2 userinfo endpoint don't match.
Steps To Reproduce
No response
Environment
No response
openvpn-auth-oauth2 logs
No response
openvpn server logs
No response
Anything else?
No response