Secret Management

The Secret Management setting gives facility to prevent the database-related or any other sensitive/confidential information from getting exposed. In Secret Management Setting We just configure the Key of the Sensitive data but the actual value is saved in Kubernetes as Environmental Variable by the DevOps Team.

  • Click on the Secret Management icon from the Configuration Admin option.

  • The Secret Management page opens.

  • Click on the New option to add a new secret.

  • Click on the Add New Field icon for the Secret Management option.

  • The option to add Secret Key Will come as shown below images.

  • Click the Save option.

  • A confirmation appears.

  • The secret will be saved and displayed the list as below.

  • To add any field click on the + icon in front of the Secret (Mongo) as shown below images.

  • Add multiple fields inside this secret like Port, Host, Username, Password, etc depending upon the requirement.

  • Once We have added all the required fields, click the Save option to save all the fields of Secret.

  • A confirmation message appears.

Please Note:

Steps to Share a Secret Key

  • Click the Share icon for a saved Secret Key.

  • The Share Secret Key window opens.

  • Select the USER or USER GROUP option to list the users (Use the EXCLUDE USER to exclude the user from the right to access a shared Secret Key).

  • Select User(s)/User Group(s) from the list.

  • Use arrow to move the selected user(s) and user group(s) to the right side box.

  • Once the selected user(s) and user group(s) appear in the right side box.

  • Click the Save option.

  • A confirmation message appears and the Secret Key gets shared to the selected user(s) or user group(s).

Please Note:

Once Configuration is done Admin needs to request the DevOps team to add the actual keys in the Kubernetes. The names of the Keys should be in the below format:


Once the DevOps has been configured the secret key’s value can be used in any module. For Reference check the DSLAB Module.

Hence, We can see that the actual value of Mongo-related fields is not exposed anywhere in the platform.

Last updated