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

Clarify Basic auth token generation

Browse Source 
Signed-off-by: Julio Zynger <julio.zynger@soundcloud.com>
This commit is contained in:
Julio Zynger
2022-01-03 15:30:16 +01:00
parent e783290cdd
commit 8ca42b7b49
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
app-config.yaml
+1 -1
View File
@@ -112,7 +112,7 @@ proxy:
allowedMethods: ['GET']
allowedHeaders: ['Authorization']
headers:
Authorization: Basic ${GOCD_AUTH_TOKEN}
Authorization: Basic ${GOCD_AUTH_CREDENTIALS}
organization:
name: My Company
plugins/gocd/README.md
+2 -2
View File
@@ -34,7 +34,7 @@ metadata:
gocd.org/pipelines: '<NAME OF THE PIPELINE 1>[,<NAME OF PIPELINE 2>]'
```
The plugin requires to configure a GoCD API proxy with a `GOCD_AUTH_TOKEN` for authentication in the [app-config.yaml](https://github.com/backstage/backstage/blob/master/app-config.yaml):
The plugin requires to configure a GoCD API proxy with a `GOCD_AUTH_CREDENTIALS` for authentication in the [app-config.yaml](https://github.com/backstage/backstage/blob/master/app-config.yaml). Its value is an opaque token you can obtain directly from your GoCD instance, in the shape `base64(user + ':' + pass)`. For example, a user "root" and password "root" would become `base64('root:root') = cm9vdDpyb290`:
```yaml
proxy:
@@ -43,7 +43,7 @@ proxy:
allowedMethods: ['GET']
allowedHeaders: ['Authorization']
headers:
Authorization: Basic ${GOCD_AUTH_TOKEN}
Authorization: Basic ${GOCD_AUTH_CREDENTIALS}
```
You should also include the `gocd` section to allow for the plugin to redirect back to GoCD pipelines in your deployed instance: