Strong Network Docs

Appearance

Integration Page ​

In the Integration Page you can manage the different access keys, secrets and tokens that are linked to the user's profile. This includes Code Repository Tokens, Personal SSH Identity and GPG Keys. The keys and tokens are used to authenticate and authorize access to different services, such as remote repository applications. By managing their keys, tokens and secrets in one location, users can easily keep track of which ones are being used, for what purpose and can revoke or add new ones as needed. The page also allows the user to view, create, and remove them, to manage access levels and to have an overview of their expiration date. This helps to ensure that only authorized users have access to the necessary resources and services, and that access is revoked when necessary.

Code Repository Tokens ​

Under Code Repository Tokens, you can configure authentication, using OAuth Authentication Tokens or Personal SSH Keys, to the following git providers:

  • GitHub,
  • GitLab,
  • and Bitbucket. For certain of these git providers, you have the option to choose between the 'Default' or 'Internal' options. An 'Internal Service' is self-hosted, whereas a 'Default Service' is hosted on the cloud.

repository-tokensCode Repository Tokens Panel

Personal SSH Identity ​

You can generate a personal SSH key to authenticate yourself when accessing external resources. The SSH key will be applied to new or existing workspaces.

ssh-identityPersonal SSH Identity Panel

GPG Keys ​

You can generate and automatically deploy GPG keys to authenticate your commits on supported Git repository applications (i.e. GitHub).

gpg-keysGPG Keys Panel