2.6 Secret

The qaskx-cli setup secret --help command is an optional step that you could perform.

The secret subcommand is used to configure your secret storage. You may have an existing secret process such as using HashiCorp Vault feature.

For all the options under this subcommand please refer to setup secret

The secret methods available will depend what your organisation offers and your Operating System.

Microsoft Windows

For the initial setup under Microsoft Windows we will use the native Credential Manager capability also know as wincred.

As an example, you can execute the following commands in Powershell terminal to create a secret keyed by DB and with User name MYUSERNAME. You will be prompted to enter your secret on the command line.

qaskx-cli   setup secret --provider wincred --org QASKX --user MYUSERNAME --key FAKEDB --tag something

	      ______           ___           _______. __  ___ ___   ___ 
	     /  __  \         /   \         /       ||  |/  / \  \ /  / 
	    |  |  |  |       /  ^  \       |   (----`|  '  /   \  V  /  
	    |  |  |  |      /  /_\  \       \   \    |    <     >   <   
	    |  `--'  '--.  /  _____  \  .----)   |   |  .  \   /  .  \  
	     \_____\_____\/__/     \__\ |_______/    |__|\__\ /__/ \__\ 
																   															 
	
          qaskx-cli  - command line tool 
          version     - 0.0.5
          url         - https://docs.qaskx.one/qaskx-cli/
          copyright   - 2023 qaskx.one, usage license limited


v Credential: Ôûê

After completing the command and supplying a secret you can view the “FAKEDB” entry in Windows using the Credential Manager in the Control Panel. After viewing the entry in Credential Manager you can remove it.

In your Windows Credential Manager you should see other entries like ones for Github, git, OneDrive.

Linux Ubuntu

Instructions under Linux Ubuntu are not available. Please refer to this location in future.

Apple iOS

Instructions under Linux Ubuntu are not available. Please refer to this location in future.

Explanation

You might be asking why not enter the secret directly in the credential provider.

The reason is that a secret’s directory file is created in the .qaskx folder that contains the links to the credential provider key. The secret’s directory file can be overriden by specifying the –vault argument.

It is the links that are checked by the qaskx-cli command to find the full path to the secret.