If you are using OpenVPN Access Server you can disable the google auth on a per user basis by modifying the user database directly. There are a number of scripts located in \/usr\/local\/openvpn_as\/scripts (debian default), one of the commands that allows database modification\/viewing is ‘confdba’. This is how I disabled the auth temporarly on a user. You could also use the dba command tool to retrive the authenticator secret, due to it not being stored in encrypted fashion. While passwords are encrypted\/hashed in db, the google auth secret is not.<\/p>\n
Code:
\n# cd \/usr\/local\/openvpn_as\/scripts
\n# .\/confdba -us -p <username> # Retrive current user properties
\n# .\/confdba -u -m -k pvt_google_auth_secret_locked -v false -p <username> # Disable Google Auth for User<\/p>\n
\nAfter executing the above, the user should be able to login to the web connect to retrieve their google auth app, or rescan their qr code. BE VERY CAREFUL when modifying the database, you could seriously screw up your database if you don’t know what you’re doing, requiring a complete reinstall.<\/p>\n
SSLCERTS From<\/strong> <\/p>\n http:\/\/docs.openvpn.net\/how-to-tutorialsguides\/administration\/cs-ca_bundle-cs-priv_key-cs-cert\/<\/p>\n \nManaging SSL Web Certificates from the CLI Managing SSL Web Certificates from the CLI<\/p>\n Currently it is not possible to backup your SSL certificates over the Admin UI. That being said, it can be easily done via the CLI. In order to do so, you will need SSH access to your Access Server. Start PuTTY and connect to the IP address of your server on port 22, SSH, and click ‘Open’.<\/p>\n Enter the server’s username and password. It must have root access. This is not the VPN client username!<\/p>\n Execute command: cd \/usr\/local\/openvpn_as\/scripts\/<\/p>\n To backup the existing CA bundle, private key, and server certificate:<\/p>\n CA Bundle:<\/p>\n Execute command: .\/confdba -gk cs.ca_bundle<\/p>\n Scroll up (if necessary), and start selecting from —–BEGIN CERTIFICATE—–, stop the selection when you hit the last —–END CERTIFICATE—–.<\/p>\n The CA bundle is now copied to the clipboard. Open up a text editor, paste the contents into the editor, and then save the file as ca.crt.<\/p>\n Private Key:<\/p>\n Execute command: .\/confdba -gk cs.priv_key<\/p>\n Scroll up (if necessary), and start selecting from —–BEGIN RSA PRIVATE KEY—–, stop the selection when you hit —–END RSA PRIVATE KEY—–.<\/p>\n The Private Key is now copied to the clipboard. Open up a text editor, paste the contents into the editor, and then save the file as server.key.<\/p>\n Server Certificate:<\/p>\n Execute command: .\/confdba -gk cs.cert<\/p>\n Scroll up (if necessary), and start selecting from —–BEGIN CERTIFICATE—–, stop the selection when you hit —–END CERTIFICATE—–.<\/p>\n The Server Certificate is now copied to the clipboard. Open up a text editor, paste the contents into the editor, and then save the file as server.crt.<\/p>\n To install the CA bundle, private key, and server certificate from a backup:<\/p>\n CA Bundle (if you self-signed your server certificate without a CA, please use your server certificate as a CA bundle): Type the follow command (but do not press Enter yet, notice the single quote at the end of the line): .\/confdba -mk cs.ca_bundle -v ‘<\/p>\n If using PuTTY, right click the terminal to paste the contents of the CA Bundle onto the terminal window.<\/p>\n After the contents of the CA Bundle is pasted into the terminal window, enter another single quote, followed by the Enter key.<\/p>\n The CA Bundle is now restored.<\/p>\n Private Key: Type the follow command (but do not press Enter yet, notice the single quote at the end of the line): .\/confdba -mk cs.priv_key -v ‘<\/p>\n If using PuTTY, right click the terminal to paste the contents of the Private Key onto the terminal window.<\/p>\n After the contents of the Private Key is pasted into the terminal window, enter another single quote, followed by the Enter key.<\/p>\n The Private Key is now restored.<\/p>\n Server Certificate: Type the follow command (but do not press Enter yet, notice the single quote at the end of the line): .\/confdba -mk cs.cert -v ‘<\/p>\n If using PuTTY, right click the terminal to paste the contents of the Server Certificate onto the terminal window.<\/p>\n After the contents of the Server Certificate is pasted into the terminal window, enter another single quote, followed by the Enter key.<\/p>\n The Server Certificate is now restored.<\/p>\n Restart the Access Server completely by invoking the following command: \/etc\/init.d\/openvpnas restart<\/p>\n If the certificates were installed correctly, the server should start without a problem. On the other hand, invalid certificates installed on the server will block the server from starting. To validate that the certificate is properly installed, visit the Web Server section in the Admin UI<\/p>\n Disabling the Lock Out aka (bootstrap) account (optional)<\/strong> Enter the command: nano \/usr\/local\/openvpn_as\/etc\/as.conf You may choose to reenable this feature at any time by removing the #sign from the aformentioned file and restarting Access Server. If you are using OpenVPN Access Server you can disable the google auth on a per user basis by modifying the user database directly. There are a number of scripts located in \/usr\/local\/openvpn_as\/scripts (debian default), one of the commands that allows database modification\/viewing is ‘confdba’. This is how I disabled the auth temporarly on a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":70,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-414","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/pages\/414","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=414"}],"version-history":[{"count":0,"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/pages\/414\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=\/wp\/v2\/pages\/70"}],"wp:attachment":[{"href":"https:\/\/www.bartons.org.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nLast modified: 24 December 2011<\/p>\n
\nYou can also take advantage of the CLI to also transfer SSL certificates across different Access Server instances, or to install new ones you’ve purchased from a SSL certificates vendor or self-signed with OpenSSL.
\nPlease note the following instructions will ONLY work when you have an actual certificate (not the built-in self-signed one) installed on your server!
\nIn addition, NO ERROR CHECKING will be performed on the certificates if they are installed this way. You could render your server UNUSABLE if the correct certificates are not installed.<\/p>\n
\nTo begin, you will need to launch a SSH client such as PuTTY to connect to your server using SSH:<\/p>\n
\nOpen up the CA Bundle file in a text editor, then copy all the contents of that file to the clipboard.<\/p>\n
\nOpen up the Private Key file in a text editor, then copy all the contents of that file to the clipboard.<\/p>\n
\nOpen up the Server Certificate file in a text editor, then copy all the contents of that file to the clipboard.<\/p>\n
\nIf you would like to revert back to the original built-in self-signed certificate after an installation of custom SSL certificates have failed, execute the following commands:
\n.\/confdba -mk cs.ca_bundle
\n.\/confdba -mk cs.priv_key
\n.\/confdba -mk cs.cert
\n\/etc\/init.d\/openvpnas restart<\/p>\n
\nIn the setup wizard, you were prompted to create an initial username and password that allowed you to login to the Admin Web UI. This username and password combination will always be active disregarding its status in the “User Permissions”area. This might be undesirable if your server is facing the Internet since anyone who has this username and password combination will have full administrator rights to change any setting on your Access Server Admin Web UI. After you have created a secondary administrator account in the Admin Web UI, you may disable this lock out account by following the steps below:<\/p>\n
\nPress the Page Down key on your keyboard and scroll down with your Down arrow key until you see entries starting with boot_pam_users.
\nPut a # sign before the entry correlating to the bootstrap username you have created previously. Usually this is the boot_pam_users.0= entry. DO NOT put a # sign before the boot_pam_service entry. Doing so will cause unexpected behaviors in your VPN server.
\nPress CTRL+O, and then press Enter. Then press CTRL+X to exit the editor.
\nRestart the VPN server by entering the following command: \/etc\/init.d\/openvpnas restart<\/p>\n
\nUpdating Operating System Software (recommended)
\nFrom the time we have generated the appliance and the time you have downloaded and are using the appliance, many operating system updates might have became available. To make sure your appliance operating system is up to date, execute the following command: apt-get update && apt-get upgrade<\/p>\n","protected":false},"excerpt":{"rendered":"