Skip to content

Commit

Permalink
Update modules/administration-guide/pages/trusted-extensions-for-micr…
Browse files Browse the repository at this point in the history
…osoft-visual-studio-code.adoc

Co-authored-by: Jana Vrbkova <jvrbkova@redhat.com>
  • Loading branch information
vitaliy-guliy and deerskindoll authored Apr 9, 2024
1 parent 5a68f97 commit 5ac77f9
Showing 1 changed file with 2 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ You can use the `trustedExtensionAuthAccess` field in the `product.json` file of

This is particularly useful when you have extensions that require access to services such as GitHub, Microsoft, or any other service that requires OAuth. By adding the extension IDs to this field, you are granting them the permission to access these tokens.

You can define the variable in the devfile or in the ConfigMap. Pick the option that better suits your needs.
With a ConfigMap, the variable will be propagated on all your workspaces and you do not need to add the variable to each the devfile you are using.
[WARNING]
====
Use the `trustedExtensionAuthAccess` field with caution as it could potentially lead to security risks if misused. Give access only to trusted extensions.
Expand Down

0 comments on commit 5ac77f9

Please sign in to comment.