paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 32 Packages Projects Releases Wiki Activity

update documentation

Browse Source 
Signed-off-by: Spencer Post <spencer.post@guildeducation.com>
This commit is contained in:
Spencer Post
2024-03-29 13:51:03 -06:00
parent 269b4c1786
commit 9a0859a0d3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/auth/atlassian/provider.md
+3 -3
View File
@@ -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