Configuring the OneFuse Appliance

Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)

In my previous article “Deploying the OneFuse Appliance”, we deployed OneFuse and was able to login to begin the configuration. 

In this article, we are going to configure a few useful items within the OneFuse platform that will be used when we begin to configure the modules for specific integrations.

We are going to configure the following items:

  • Add a new user and grant them admin privileges
  • Configure a DNS Endpoint
  • Create a Static Property Set to simulate inputs

Adding Users

We are going to walk through how to create and entitle users in the workspace. 

  1. To begin, you will need to select the wrench in the upper right corner of the page header.
  2. Next, select “User Management from the Administration menu.
  3. Once under the “User Management” menu, select “Create”.
  4. Next, enter a Username, Email Address, First Name, Last Name, and Password for the new user.  Then, select “Configuration Administrator” if you wish to grant the user administrator permissions.
  5. Once completed, select “Return to workspace” from the page header.
  6. Once you are back to the main screen, you will need to expand “Workspace Admin” on the lower section of the left menu and then select “User Management”.
  7. Once in the “Workspace User Management” page, select “ADD” to add a new user to the workspace.
  8. Here, you will select from the user(s) you created in the previous steps.  This allows us to take the locally created user and assign them a role within the workspace.  Once you select the user you want to entitle you can then select from the Admin, Member, and Viewer role.  Admins can create policies, Members can consume policies, and viewers can view policies.  Policies will be discussed in more detail in future articles.  Select “Add” to add the user to the workspace.

That completes adding a user and entitling them to the default workspace

Creating a DNS Endpoint

In this section, we are going to create a simple DNS endpoint that we can use to query against for hostname validation with the OneFuse Naming module. 

  1. To begin, select “Module Endpoints” for the left-hand menu.
  2. Next, select “Create” and then select “DNS” from the menu.
  3. On the “Create a DNS Endpoint” page, give the endpoint a name, a description, and then input the DNS host you would like to use for validation.  This can be a domain, the FQDN of a DNS server, or an IP address of a DNS server.
  4. When finished, select “Create” to finalize the creation of the endpoint.  Repeat the process for any additional DNS endpoints you would like to add.

Next, we are going to create a OneFuse Static Property Set.  Static Property Sets have many uses.  The Static Property Set we will be creating will be used to validate configurations that we create within the UI.  This use of the Static Property Set for this purpose will be covered in the next article.

Creating a OneFuse Static Property Set

The Static Property Set we are going to create in this example is going to be utilized to simulate inputs that would be passed into OneFuse as part of a request.  This will allow us to perform inline testing of certain values within OneFuse as we create our policies for the different modules.

  1. Expand Templating on the left menu and select “Static Property Sets”.
  2. Select “Create” to create a new Static Property Set.
  3. Next, give your Static Property Set a meaningful name.  We are then going to add name/value pairs to the property set.  Static Property Sets use standard JSON formatting when inputting data.
  4. Once you are finished creating your Static Property Set, select “Create”.

Example Static Property Set:

  "nameGroup": "pp",
  "nameLocation": "atl",
  "nameEnv": "prod",
  "nameOS": "l",
  "nameApp": "web",
  "dns_zone": ""

Now that we have learned how to create and entitle users, add a DNS endpoint, and we have created a Static Property Set, we can move on to creating policies within the modules.  

Check out my next article “Creating a OneFuse Naming Policy” where we will be creating Naming Policies that can be used to name resources and deployments.

Visit for more information and to join the OneFuse Community Forum