the_crowbar
Hello,
I have an OpenVPN AS server in Amazon EC2. I started the instance from the 2.0.11 AMI, but I upgraded OpenVPN AS and the base system today.
I am using LDAP for user authentication and I have a post auth script that sets the group based on LDAP group membership.
Today I purchased several licenses and sent the URL to some testers. I got immediate error reports back. No one was able to access the servers using the OpenVPN server.
I think I have narrowed down the issue somewhat. I had done my testing with the stand OpenVPN client and the config file that can be downloaded by logging into th AS server.
The testers were downloading the OpenVPN Connect client.
From looking in the logs, my post auth script gets called twice when connecting with the Connect client, but only once when connecting using the standard OpenVPN client.
The second call to the post auth script, the Connect user gets assigned to the default group rather than the one previously set by my script. Because the second call is not an LDAP auth (and there is no LDAP context available) the post auth script does not do anything but log output.
Can anyone point in the rght direction here?
My script runs once and sets the correct group, then it is called again but does nothing except log the current group and it is the default user group.
Thank you,
James
jjeffers
Same behavior here. I was beating my head against the wall trying to figure out what I was doing wrong for hours. Then it turns out the damn client is running the post_auth script twice. WTF.
James, did you ever figure this out?
