Skip to content

Create a new Barracuda WAF machine

Preview feature

This feature is available in Preview and isn't yet generally available (GA). Functionality and behavior can change before GA.

Creating a machine enables Certificate Manager - SaaS to connect to a Barracuda Web Application Firewall (WAF) so it can discover the certificates stored on the appliance and provision certificates to its services. After creating the machine, you can discover and provision certificates.

Before you begin

  • The hostname or IP address of the Barracuda WAF management interface.
  • The administration port. The default is 8000.
  • An active VSatellite with network access to the Barracuda WAF management interface on that port.
  • An appliance account with read and write access to certificates and services. Full administrator access isn't required.
  • (Optional) Shared credentials stored in a supported credential provider.
  1. In Server Hostname, enter the hostname or IP address of the Barracuda WAF management interface.

  2. If the appliance uses a port other than 8000, enter the port number in Port.

    Important

    The port determines the protocol. Certificate Manager - SaaS connects over HTTPS only on port 443. On any other port, it connects over plain HTTP:

    • Port 8443: Barracuda WAF commonly serves HTTPS on 8443, but Certificate Manager - SaaS connects to that port over plain HTTP. Because the protocols don't match, Test Access fails. To connect over HTTPS, the appliance must serve HTTPS on port 443.
    • Port 8000 (the default) and other HTTP ports: the connection works, but the sign-in credentials and private keys are sent unencrypted.

    There's no separate setting for the protocol.

    Note

    Over HTTPS, the connection is encrypted, but Certificate Manager - SaaS doesn't verify the appliance's certificate. As a result, appliances that use a self-signed management certificate connect without extra configuration.

  3. From Credential Type, select one of the following:

    • Enter Credentials to provide credentials manually.
    • Select Credentials to use shared credentials from a configured credential provider.

    Note

    Credential types require additional licensing. The available credential options depend on your environment configuration.

  4. If you selected Enter Credentials, enter the appliance account's Username and Password.

    Warning

    Remember to store your username and password securely when creating a new machine. For security reasons, you will not be able to modify the fields under the "Access" tab without these credentials. This ensures that only authorized individuals can modify these fields.

  5. If you selected Select Credentials, choose the appropriate credential from the Credential list.

  6. Click Test Access to verify connectivity.

    Note

    Test Access confirms only that Certificate Manager - SaaS can sign in. It doesn't check the account's permissions, so an account without read and write access to certificates and services passes the test but fails during discovery or provisioning. If the test fails, check the hostname, the credentials, and that the port matches the protocol the appliance serves on it: HTTPS on 443, plain HTTP on any other port.

  7. Click Continue. The Continue button is enabled only after the connection test succeeds.

What's next?