Nethvoice Proxy UI: Add Let's Encrypt On/Off Toggle

[Amygos]

Proposed Feature
Implement a user interface (UI) toggle in the Nethvoice Proxy module for enabling or disabling Let's Encrypt certificate management.

Purpose and Motivation
The new backend flag for controlling Let's Encrypt has been introduced to allow administrators to enable or disable certificate validation as needed. To comply with user experience guidelines and provide clear visibility and control, the UI must expose this capability as an intuitive toggle.

Proposed Solution

• Add an on/off toggle in the Nethvoice Proxy module UI for Let's Encrypt certificate management.
• Ensure the toggle accurately reflects and controls the backend state via the newly added flag.
• Display any necessary warnings or status messages in line with NethServer 8 certificate management guidelines, including Traefik restart warnings when applicable.

Alternative Solutions

• Continue without a UI toggle, maintaining the previous behavior where Let's Encrypt is always enabled. This is not recommended as it does not provide sufficient user control or feedback.

Additional Context

• This feature depends on backend changes tracked in issue Nethvoice Proxy: Add Let's Encrypt On/Off Flag to Nethvoice Proxy Module Backend #7700.
• Follow updated UX guidelines for certificate management and ensure seamless integration with backend state. See the a reference UI mockup.

See also

• Parent issue: NethVoice Let's Encrypt validation enhancement #7670

[Amygos]

Test Case 1: Configure with a valid FQDN and Let's Encrypt enabled

• Objective: Verify that the system can successfully obtain a Let's Encrypt certificate when the feature is enabled with a valid, publicly resolvable FQDN.
• Preconditions:
  • The ns8-nethvoice-proxy module is installed from the testing repository.
  • You have a valid FQDN that resolves to the server's public IP address.
  • Ports 80 and 443 are open and forwarded to the NethServer instance.
• Steps:
  1. Navigate to the Nethvoice Proxy module UI.
  2. Enter the valid FQDN into the designated field.
  3. Ensure the "Let's Encrypt certificate" toggle is turned ON.
  4. Save the configuration.
• Expected Results:
  • The configuration is saved successfully without any errors.
  • A warning is displayed informing the user that Traefik needs to be restarted for the changes to take effect.
  • After the Traefik restart, the FQDN should be accessible via HTTPS with a valid Let's Encrypt certificate.

Test Case 2: Configure with an invalid FQDN and Let's Encrypt enabled

• Objective: Verify that the system shows an error when trying to obtain a Let's Encrypt certificate for an FQDN that is not publicly resolvable.
• Preconditions:
  • The ns8-nethvoice-proxy module is installed from the testing repository.
  • You have an FQDN that does not resolve to the server's public IP (e.g., a local-only domain or a fake one).
• Steps:
  1. Navigate to the Nethvoice Proxy module UI.
  2. Enter the invalid/unresolvable FQDN.
  3. Ensure the "Let's Encrypt certificate" toggle is turned ON.
  4. Save the configuration.
• Expected Results:
  • The save operation fails.
  • An ACME challenge error (newcert_acme_error) is displayed, informing the user that the certificate could not be validated.
  • The configuration is not applied.

Test Case 3: Configure with Let's Encrypt disabled

• Objective: Verify that the system accepts the configuration without attempting certificate validation when the Let's Encrypt toggle is disabled.
• Preconditions:
  • The ns8-nethvoice-proxy module is installed from the testing repository.
• Steps:
  1. Navigate to the Nethvoice Proxy module UI.
  2. Enter any FQDN (valid or not).
  3. Ensure the "Let's Encrypt certificate" toggle is turned OFF.
  4. Save the configuration.
• Expected Results:
  • The configuration is saved successfully without any validation errors.
  • A warning is displayed informing the user that Traefik needs to be restarted for the changes to take effect.
  • After the restart, the route is active, but no Let's Encrypt certificate is provisioned. Accessing the FQDN will likely result in a certificate warning from the browser, using the cluster's default certificate.

Test Case 4: Upgrade from stable to testing

• Objective: Verify that the module updates correctly and the new UI toggle is present and functional.
• Preconditions:
  • The ns8-nethvoice-proxy module is installed from the stable repository.
• Steps:
  1. Configure the module with a valid FQDN.
  2. Ensure the Software Center is pointing to the testing repositories.
  3. Upgrade the ns8-nethvoice-proxy module to the latest testing version.
  4. After the upgrade, navigate to the Nethvoice Proxy module UI.
• Expected Results:
  • The module upgrades successfully.
  • The new "Let's Encrypt certificate" toggle is visible in the UI.
  • The previous FQDN configuration is preserved.
  • The toggle's default state should be consistent with the expected behavior (likely ON after a successful configuration, or OFF if never configured before). You should be able to enable it and save the configuration as in Test Case 1.