Migration to 2.0 wizard

[kchudy]

• Detect that it's a migration and not a fresh instance.
• Use the configuration options from .env to prefill the wizard forms.
• After the user confirms the wizard, move the config options to the database.
• Inform the user that the configuration was moved to the database, and the configuration placed in env variables or config files is obsolete.

[kchudy]

@Va1ter Please provide design

[teon]

@kchudy to little information for a design. Which data will be frefilled?

There is lack of info that there will be migration of locations...

@Va1ter lets have a session and I will explain - you take notes here.

[teon]

@Va1ter here are specific parts to be included in the design. The most important part is that we keep the initial design but do some slight changes when we detect that this is not an initial setup but migration:

1. On welcome screen, we need to show:

Welcome to 2.0 this is a migration since we have detected version X.y.Z and N locations.
First of all we will upgrade core and proxy (now called Edge Component) and then each location will need some changes on your internal network (on your firewalls) for new core<->gateway communication. We will guide you step by step. But you can get familiar with migration in details here in the documentation https://docs.defguard.net/2.0-migration-guide.

IMPORTANT: Until you finish this migration process your VPN Locations will not work!.

2. There will bo no "Create password step"
3. Step three will be "Confirm your general configuration" current detected options.
4. Step 4 will have to have additional information:

We have incorporated Certificate Authority (CA) management into Defguard to simplify component deployment and ongoing management.

FOR DEV: If we detect that Core already has certificates configured, we will display the following message:

We have detected that your component communications are already secured with SSL certificates. However, we strongly recommend creating a new Certificate Authority managed by Defguard to simplify future deployments.

If you choose to retain your existing certificates, Defguard can import them for all components that currently use SSL. Please note that when you create a new VPN location or add a new Edge component (formerly Proxy), you will need to manually configure certificates on those components using your existing Certificate Authority.

5. Edge Component (step 5) we need to add:

Starting with Defguard 2.0, the Proxy has been renamed to the Edge component, and support for deploying multiple instances for high availability has been introduced. We have detected your current Proxy setup. Please upgrade your Proxy to the latest 2.0 Edge component so it can be adopted and configured by Defguard.

Now after finishing this wizard we need to inform that each detected location has to be upgraded:

You currently have X VPN locations configured. These locations must be upgraded.

One important architectural change in Defguard 2.0 is that the Core now initiates connections to the gateways (in version 1.x, the gateways connected to the Core). As a result, in addition to upgrading the gateway components, you must update your firewall rules to:

• Allow connections from the Core to the gateways on port 5055
• Block connections from the gateways to the Core

This final architectural change significantly improves the overall security of Defguard deployments. You can read about this in documentation here XXX.

Please prepare all required network and firewall changes before beginning the migration process, then we will begin the adoption process of upgraded gateway components for each VPN Location.

Now we need a new custom wizard? Step? Informing:

Beginning the location: XYZ upgrade process (1 of 5 locations). By clicking next we assume your firewall changes have been made and Core can connect to this gateway on port 5055.