The Sensedia CLI Token is an access code used to authenticate the Sensedia CLI with the Sensedia API Platform.
It must be generated from the Sensedia API Platform graphical interface following the steps below.
On the API Manager screen, click on the button with your user information, located in the upper right corner:

A modal window for editing the profile will open.
Click the CREATE CLI TOKEN button.

Copy the code that will be displayed in the CLI Token field.
That is the code that has to be passed with the --token flag of the ssd configure command of Sensedia CLI.
CAUTIONThe Sensedia CLI Token is only visible at the time it is generated. After closing the profile editing window, it will no longer be possible to view it. Therefore, it is recommended to copy it immediately. If necessary, you can revoke it and generate a new token, following the steps below.
You can revoke (i.e. disable) the Sensedia CLI token at any time by clicking the REVOKE button as shown in the figure below. This will permanently prevent Sensedia CLI from making requests to Sensedia API Platform with this token. To authenticate Sensedia CLI again, you will need to generate a new token by repeating the steps above.

ssd logout)The ssd logout command can be followed by flags with their respective arguments:
If no flag is specified, the interactive mode will be activated.
Flag | Type | Description |
|---|---|---|
| -h, --help | Displays help for the command | |
| -y, --yes | Skips the confirmation step |
Flag | Tipo | Descrição |
|---|---|---|
| -c, --config | string | Arquivo de configuração (predefinido: $HOME/.sensedia/config.json) |
| --profile | string | Perfil de configuração que deseja utilizar (predefinido: "default") |
| --verbose | Lista todas as requisições feitas pelo comando. É possível armazenar essas informações em um arquivo TXT em vez de exibi-las no terminal. Ex.: $ ssd (api-management | apim) list apis --verbose 2> log.txt |
NOTEThe Sensedia CLI Token has no expiry time.
Sensedia CLI Token and changes in access permissions
If new access permissions are granted, the user must generate a new Sensedia CLI Token for the new permissions to take effect;
If permissions are removed, the administrator must revoke the current Sensedia CLI Token for the user to lose these permissions.
To revoke the current Sensedia CLI Token and generate a new one, follow the steps described above.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more