[DOC] Fix broken link to cookie secret generation (#1024)
* [DOC] Fix broken link * Update auth.md * Update auth.md * Update auth.md Co-authored-by: Joel Speed <Joel.speed@hotmail.co.uk>
This commit is contained in:
		
							parent
							
								
									0f859215f0
								
							
						
					
					
						commit
						7def4bf360
					
				|  | @ -163,7 +163,7 @@ Whether you are using GitLab.com or self-hosting GitLab, follow [these steps to | ||||||
| 
 | 
 | ||||||
| If you need projects filtering, add the extra `read_api` scope to your application. | If you need projects filtering, add the extra `read_api` scope to your application. | ||||||
| 
 | 
 | ||||||
| The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/docs/configuration/configuration.md#configuration) | The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](./overview.md#generating-a-cookie-secret) | ||||||
| 
 | 
 | ||||||
| ``` | ``` | ||||||
|     --provider="gitlab" |     --provider="gitlab" | ||||||
|  |  | ||||||
|  | @ -149,7 +149,7 @@ The group management in keycloak is using a tree. If you create a group named ad | ||||||
| 
 | 
 | ||||||
| Whether you are using GitLab.com or self-hosting GitLab, follow [these steps to add an application](https://docs.gitlab.com/ce/integration/oauth_provider.html). Make sure to enable at least the `openid`, `profile` and `email` scopes, and set the redirect url to your application url e.g. https://myapp.com/oauth2/callback. | Whether you are using GitLab.com or self-hosting GitLab, follow [these steps to add an application](https://docs.gitlab.com/ce/integration/oauth_provider.html). Make sure to enable at least the `openid`, `profile` and `email` scopes, and set the redirect url to your application url e.g. https://myapp.com/oauth2/callback. | ||||||
| 
 | 
 | ||||||
| The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/docs/configuration/configuration.md#configuration) | The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](./overview.md#generating-a-cookie-secret) | ||||||
| 
 | 
 | ||||||
| ``` | ``` | ||||||
|     --provider="gitlab" |     --provider="gitlab" | ||||||
|  |  | ||||||
|  | @ -163,7 +163,7 @@ Whether you are using GitLab.com or self-hosting GitLab, follow [these steps to | ||||||
| 
 | 
 | ||||||
| If you need projects filtering, add the extra `read_api` scope to your application. | If you need projects filtering, add the extra `read_api` scope to your application. | ||||||
| 
 | 
 | ||||||
| The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/docs/configuration/configuration.md#configuration) | The following config should be set to ensure that the oauth will work properly. To get a cookie secret follow [these steps](./overview.md#generating-a-cookie-secret) | ||||||
| 
 | 
 | ||||||
| ``` | ``` | ||||||
|     --provider="gitlab" |     --provider="gitlab" | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue