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

Merge pull request #23897 from postsa/postsa/atlassian-auth-provider-fix

Browse Source 
(BUGFIX:  plugin-atlassian-auth-provider) pass scope to strategy
This commit is contained in:
Fredrik Adelöw
2024-04-10 17:49:46 +02:00
committed by GitHub
parent cc9ee28050 7a7e103882
commit e054570987
6 changed files with 128 additions and 4 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