Git Authentication - nxp-mcuxpresso/vscode-for-mcux GitHub Wiki
Sometimes, it may be necessary to access Git repositories that require authentication. For instance, custom remote repositories, that may require authentication via HTTPS or SSH key, can be imported and registered into the extension.
HTTPS Authentication
The repository can be manually typed into the input, or pasted, and an option to use that value will be displayed in the selection combo.
Upon selecting a custom repository that is private or not publicly accessible, an authentication window will appear. Depending on the configuration and authentication options of the origin SCM software, there are multiple possibilities to authenticate. Most of the time browser or password authentication will be provided.
Using Browser authentication, the user will be redirected in a new web browser page to the authentication portal of the Git website. Depending on the employed SSO flow of the organization, multiple redirects or steps may occur before successful authentication is achieved.
Using Password authentication, the user will be able to provide the credentials of the account direcly into the authentication window. The username or password may be different depending on the security policy of the organization. For instance, in some cases an application token may be required in place of a password.
SSH Authentication
SSH authentication is done using the default Git SSH Agent. This avoids having to input the SSH key passphrase multiple times when conducting Git operations.
Upon using an SSH repository URL in a control, an instance of the SSH agent will be started, if one does not exist already. If the default passphrase for the given domain is not empty, a passthrough input will be displayed in order to authenticate the SSH agent and unlock the SSH key.
If the password is incorrect, a new input will be shown. To exit the prompt, the user can press 'Enter' with an empty passphrase or 'Escape'.