From 9a0859a0d39564717e0cfb06ab80707c8ee0040f Mon Sep 17 00:00:00 2001 From: Spencer Post Date: Fri, 29 Mar 2024 13:51:03 -0600 Subject: [PATCH] update documentation Signed-off-by: Spencer Post --- docs/auth/atlassian/provider.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/auth/atlassian/provider.md b/docs/auth/atlassian/provider.md index cded6e73ca..2680370d93 100644 --- a/docs/auth/atlassian/provider.md +++ b/docs/auth/atlassian/provider.md @@ -46,16 +46,16 @@ auth: development: clientId: ${AUTH_ATLASSIAN_CLIENT_ID} clientSecret: ${AUTH_ATLASSIAN_CLIENT_SECRET} - scopes: ${AUTH_ATLASSIAN_SCOPES} + scope: ${AUTH_ATLASSIAN_SCOPES} ``` The Atlassian provider is a structure with three configuration keys: - `clientId`: The Key you generated in the developer console. - `clientSecret`: The Secret tied to the generated Key. -- `scopes`: List of scopes the app has permissions for, separated by spaces. +- `scope`: List of scopes the app has permissions for, separated by spaces. -**NOTE:** the scopes `offline_access` and `read:me` are provided by default. +**NOTE:** the scopes `offline_access`, `read:jira-work`, and `read:jira-user` are provided by default. ## Adding the provider to the Backstage frontend