Vault

OmniDeq vault manages all the credentials used during OmniDeq operations.

OmniDeq accepts different types of credentials such as:

  1. AWS
  2. Google Cloud
  3. SSH Key
  4. Username and Password
  5. Azure
  6. Docker Config
  7. JSON
  8. Kerberos Config
  9. Red Hat
  10. Dynatrace
  11. New Relic
  12. DataDog
  13. Build Box
  14. Container Registry

Go to Vault

You can go to Vault page by clicking on "Settings" menu to get drop down options and select the Vault submenu, as shown in image below Go to Vault

Add a vault

To create the vault click on Add Vault button on the right side as shown in the image below with appropriate type.

Create Vault

AWS

  1. Supply the appropriate values and click on Save button.

AWS Vault

Field Name Description
Name Supply desired name here
Vault Type Select AWS
Access Key Enter Access key for AWS account
Secret Key Enter Secret key for AWS account

Note :

   

Google Cloud

  1. Supply the appropriate values and click on Save button.

Google Cloud Vault

Field Name Description
Name Supply desired name here
Vault Type Select Google Cloud
Google Config JSON Upload the Config JSON file from your machine
Google Project Id Enter Project Id

  2. The vault will be added in the list of vaults.

   

SSH Key

  1. Supply the appropriate values and click on Save button.

SSH Key

Field Name Description
Name Supply desired name here
Vault Type Select SSH Key
SSH Key Upload the SSH Key (.Pem/ *_rsa file) from your machine
  1. The vault will be added in the list of vaults.

   

Password

  1. Supply the appropriate values and click on Save button.

Password Vault

Field Name Description
Name Supply desired name here
Vault Type Select Password
Username Enter Username
Password Enter Password

Notes :

   

Azure

  1. Supply the appropriate values and click on Save button.

Azure Vault

Field Name Description
Name Supply desired name here
Vault Type Select Azure
Subscription Id Enter Azure Subscription Id
Tenant Id Enter Azure Tenant Id
Client Id Enter Azure Client Id
Client secret key Enter Client secret key
Client URL Enter Azure Client URL

Notes :

   

Docker Config

  1. Supply the appropriate values and click on Save button.

Docker Vault

Field Name Description
Name Supply desired name here
Vault Type Select Docker Config
Docker config JSON Upload valid docker config JSON file
  1. The vault will be added in the list of vaults.

JSON

  1. Supply the appropriate values and click on Save button.

Json Vault

Field Name Description
Name Supply desired name here
Vault Type Select JSON
JSON file upload JSON file
  1. The vault will be added in the list of vaults.

Kerberos Config

  1. Supply the appropriate values and click on Save button.

Kerberos Vault

Sample Template

[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm = <REPLACE_ME>
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
[realms]
<REPLACE_ME> = {
kdc = <REPLACE_ME>
admin_server = <REPLACE_ME>
}
[domain_realm]
.website.com = <REPLACE_ME>
website.com = <REPLACE_ME>
Field Name Description
Name Supply desired name here
Vault Type Select Kerberos config
Domain Realm Enter valid Realm
Domain Controller IP Enter valid controller IP
Domain Username Enter valid domain username
Domain Password Enter valid domain password
Kerberos config Upload kerberos config file (.conf)

Notes:

Red Hat

  1. Supply the appropriate values and click on Save button.

Red Hat Vault

Field Name Description
Name Supply desired name here
Vault Type Select Red Hat
Username Enter username
Password Enter Password
Pool Id Enter valid pool Id

Note:

Dynatrace

  1. Supply the appropriate values and click on Save button.

Dynatrace Vault

Field Name Description
Name Supply desired name here
Vault Type Select Dynatrace
Api Token Enter Api token
Pass Token Enter Pass token
Environment Id Enter Environment Id

Note:

New Relic

  1. Supply the appropriate values and click on Save button.

New relic Vault

Field Name Description
Name Supply desired name here
Vault Type Select New Relic
License key Enter license key

Note:

DataDog

  1. Supply the appropriate values and click on Save button.

DataDog Vault

Field Name Description
Name Supply desired name here
Vault Type Select DataDog
Api key Enter Api key

Note:

Build Box

  1. Supply the appropriate values.

    Build Box Vault

    Field Name Description
    Name Supply desired name here
    Vault Type Select Build Box
    Container type Select Linux or Windows
    Username Username to authenticate on Build Box
    Host Build Box IP or FQDN
    Port Build Box port
    Connection Type Enter either SSH or password
    Kerberos IP Provide kerberos IP (Active only in case of windows buildbox)
    Build Box Credentials Credential vault to connect to Build Box ( either SSH or password)


  1. For both Build Boxes that is Linux and Windows, you can see the button as Validate and Save as only valid Build Box gets saved. You can see appropriate logs as shown in below image Build Box validation logs

    Notes :

    • SSH, Password or kerberos vault can be used to store the login credentials like Windows login credentials, Docker hub login credentials, Custom registry login credentials etc.
    • Build Box username can be 20 characters long
  2. The vault will be added in the list of vaults.

Container Registry

  1. Supply the appropriate details and click on Save button.

Container Registry Vault

Field Name Description
Name Supply desired name here
Vault Type Select Container Registry
Registry Type Select DockerHub, ECR, Quay or Custom
Server Specify the appropriate Registy Server
Registry Credentials Credential vault to connect to Registry ( either SSH or password)

Note :

View, Edit and Delete Vault

  1. You can perform actions like

    • View
    • Edit
    • Delete
    • View Logs (Applicable only in case of Build box vault)
  2. Click on any of the desired action button to perform actions on respective vault. As shown in below image. Actions on vault

  3. Once you click on the icon with title View Logs from one of the actions, you can see the previous logs of the respective build box. As shown in below image. Logs at Page one