What does the CLI token feature do in partner settings?

[john_C139]

Hi,

I want to know more about the CLI Token in partner. There is a feature in Settings->CLI Token. I do not quite understand this feature. Does it mean you can configure the CLI token as an environment variable and anyone who has access right to work on this environment can work on an APP without further authentication? Except the development of APP, what else can this CLI token be used? How to keep this CLI token safe? Because if you stored in environment, developer may still can see it, right?

[oscprofessional · Accepted solution]

Hello @john_C139,

The CLI Token feature in a partner account typically allows for streamlined authentication and access to specific services or resources without the need for repeated authentication steps. Let me break down your questions:

• Understanding CLI Token in Partner Account:

  • The CLI Token essentially acts as a form of authentication token that grants access to certain functionalities or resources within the partner's environment.
  • It can be configured as an environment variable, which means it can be set within the environment and utilized by authorized users or processes.

• Access to Apps Without Further Authentication:

  • Yes, with the CLI Token configured as an environment variable, authorized users within the environment can access apps or services without the need for repeated authentication.

• Other Uses of CLI Token:

  • Apart from app development, the CLI Token can be used for various automation tasks, scripting, or integrating partner services with other platforms.
  • It might also facilitate secure communication between different components of the partner's infrastructure or enable access to partner-specific APIs or services.

• Ensuring CLI Token Security:

  • While storing the CLI Token as an environment variable can streamline access, it's crucial to ensure its security.
  • Best practices include limiting access to the environment where the token is stored only to authorized personnel.
  • Additionally, consider using encryption or secure key management solutions to safeguard the token.
  • Regularly review and rotate tokens to mitigate the risk of unauthorized access.
    
    

[john_C139]

Now it's clear for me. Thanks for your reply😀

[hackerboi101]

</h1>alert</h1>