Comment on page
Here you can track changes made in more detail than on our GitHub release page: https://github.com/DefGuard/defguard/releases
We've created a one-line install script to simplify your first defguard deployment. You should now be able to get your own instance running on a private VPS just by setting a couple environment variables and running:
curl --proto '=https' --tlsv1.2 -sSf -L https://raw.githubusercontent.com/DefGuard/deployment/main/docker-compose/setup.sh -O && bash setup.sh
The main defguard concept is that the core (with the database) should be deployed securely and not available from the public Internet (accessible only from the internal network or VPN). This approach raised a significant problem with onboarding new remote users: how can users access defguard, set up password, and add their devices to access VPN or change their password if they can't access defguard?
We introduced a public proxy that now enables a secure enrollment process, during which the user can: double-check their data, setup their password, and add their initial device to access VPN as a nice wizard!
In the future, we plan to add more functionalities to the public proxy - like password reset for users.
Now you can easily share with new users any relevant company information, links to company systems, security guidelines, etc. In the enrollment module, you can write custom messages using markdown that will be shown on the last step of the enrollment process and sent to the user via email:
In Setup -> SMTP tab you can setup and test your SMTP for sending email (for enrollment and onboarding). SMTP setup is required in order for enrollment & onboarding to work.
Now you can go to Settings -> Support and download (or send via email automatically if you have setup SMTP) support data & logs if you need our help/assistance! Or you can use them when submitting a bug.
For now, we support only 24h window into stats (more detailed stats we plan to do using OpenTelemetry and Prometheus exporter for devops/admins to configure their dashboards and all events stats according to their needs).
So a lot of stats data is gathered, not used. We need to purge them.
Implement supporting multiple VPN networks/locations
- allow only selected groups/users (currently we support two: All users & Admin) to connect to selected Location/VPN
- displaying detailed statistics for each VPN/Location
- allowing users to download the configuration for each device for any Location/VPN network
Some companies (including ours) have infrastructure requirements for their systems to support high availability/failover to secure business continuity. VPN for some companies (remote access to their systems) is critical. In defguard, the component responsible for configuring/managing VPN connections is the gateway. In order to provide HA/Failover we would need to spawn a gateway on each firewall/router and defguard would need to support multiple gateways.
Support multiple instances of gateway service in order to provide high availability/failover and display the status of each gateway: