In the documentation, it states one should create a new local admin and remove the default admin, as well as editing the as.conf to survive container recreation. This of course works, but what doesn't seem to work is when using RADIUS as the authentication method. Then the only user I can log in with (even after editing the as.conf file) is the default admin with password:password.
I thought maybe because it's using the RADIUS from the Synology the container is running on I could use the Synology admin user, but that tells me I don't have permission to access the admin panel.
I managed to figure this. Pretty simple, wasn't thinking properly. When you generate a config for a user, they will then appear in the list of users in the OpenVPN server portal, which you can then set as admin
In the documentation, it states one should create a new local admin and remove the default admin, as well as editing the as.conf to survive container recreation. This of course works, but what doesn't seem to work is when using RADIUS as the authentication method. Then the only user I can log in with (even after editing the as.conf file) is the default admin with password:password.
I thought maybe because it's using the RADIUS from the Synology the container is running on I could use the Synology admin user, but that tells me I don't have permission to access the admin panel.
Is there any way around this?
Thanks!