Linux Server

This topic contains instructions for a Linux server deployment.

Once a server is installed based on the deployment information below, it will automatically be updated when new server packages are released.

Package names:

  • hydns-[version]-[OS(-flavor)]-[architecture]

Where:

  • [version], is a number string, for example, 1.0.114 based on a recent build.
  • [OS(-flavor)], can be Linux, Windows, OSx (coming soon) with flavor and version information, like ubuntu22.04 or rhel8, for example.
  • [architecture], references the system chip information, for example, amd64.

Hydden uses port 22101 as the default Bootstrap port.

Linux Server Deployment

  1. As the root user or elevated root shell or using the sudo command with an appropriate policy, you can install the Hydden server using:

       root@US-Bunty1:/mnt/dc01# chmod +x hydns-1.0.114-linux-ubuntu22.04-amd64
       root@US-Bunty1:/mnt/dc01# hydns-1.0.114-linux-ubuntu22.04-amd64

    A successful installation and registration is confirmed with the following messages:

       2024-04-22T21:08:02.929-0400    INFO    Server installed successfully   {"pid": 217541, "name": "hydn-server"}
  2. The successful installation triggers the bootstrap process. Select your preferred browser from the modal.

    img
    Server bootstrap page

  3. Select Create a new cluster.

  4. Click Next.

  5. On the Bootstrap Hydden Server page:

    1. From the OpenID Connect Configuration drop-down select your Provider, the options are

      • Azure Multi Tenant,
      • Azure Single Tenant,
      • Google,
      • Okta, or
      • Custom

      We are using Azure Single Tenant for this example.

    2. Enter a name, for example, YourOrg-Hydden-On-prem.

    3. For Client Server, in your Azure portal app registration, navigate to Manage | Certificates & Secrets and on the Client Secrets tab, click + New client secret. Copy the secret and on the bootstrap page, paste the secret into the Client Server field.

      img
      Azure portal Certificates & Secrets page

    4. For the Client ID, in your Azure portal app registration, navigate to Overview and copy the Application Client ID. On the bootstrap page, paste the Application Client ID into the Client ID field.

      img
      Azure portal overview page

    5. In your Azure portal, navigate to Manage | Authentication and under Platform Configuration, click + Add platform, select Web.

      img
      Add platform page

      From the bootstrap page copy and paste the Redirect URL into the web platform configuration in the Azure portal. Select the “Access tokens (used for implicit flows)” and “ID tokens (used for implicit and hyrid flows)” checkboxes.

    6. For the Issuer, in your Azure portal, navigate to your organization’s “Microsoft Entra ID” Overview page and copy the Tenant ID. On the bootstrap page, for Issuer, type https://login.microsoft.com/{tenant_id}/v2.0 and replace {tentant_id} by pasting the previously copied Tenant ID into the URL.

      The Issuer URL is not required for this configuration.

      img
      Filled out bootstrap page

    7. Click Login for the auth handshake.

    8. Click Next.

      Verify your details on the final bootstrap page.

      img
      Bootstrap verification page

  6. Click Finish.