Remove the information about `Microsoft Azure AD` in the provider documentation (#1477)
* Remove the information about `Microsoft Azure AD` * Put `proxy_buffer_size` in a code tag * Update `CHANGELOG.md` Co-authored-by: Joel Speed <Joel.speed@hotmail.co.uk>
This commit is contained in:
		
							parent
							
								
									576184924d
								
							
						
					
					
						commit
						0e10fb8967
					
				|  | @ -8,6 +8,8 @@ | ||||||
| 
 | 
 | ||||||
| ## Changes since v7.2.1 | ## Changes since v7.2.1 | ||||||
| 
 | 
 | ||||||
|  | - [#1477](https://github.com/oauth2-proxy/oauth2-proxy/pull/1477) Remove provider documentation for `Microsoft Azure AD` (@omBratteng) | ||||||
|  | 
 | ||||||
| # V7.2.1 | # V7.2.1 | ||||||
| 
 | 
 | ||||||
| ## Release Highlights | ## Release Highlights | ||||||
|  |  | ||||||
|  | @ -15,7 +15,6 @@ Valid providers are : | ||||||
| - [Keycloak](#keycloak-auth-provider) | - [Keycloak](#keycloak-auth-provider) | ||||||
| - [GitLab](#gitlab-auth-provider) | - [GitLab](#gitlab-auth-provider) | ||||||
| - [LinkedIn](#linkedin-auth-provider) | - [LinkedIn](#linkedin-auth-provider) | ||||||
| - [Microsoft Azure AD](#microsoft-azure-ad-provider) |  | ||||||
| - [OpenID Connect](#openid-connect-provider) | - [OpenID Connect](#openid-connect-provider) | ||||||
| - [login.gov](#logingov-provider) | - [login.gov](#logingov-provider) | ||||||
| - [Nextcloud](#nextcloud-provider) | - [Nextcloud](#nextcloud-provider) | ||||||
|  | @ -87,7 +86,7 @@ Note: The user is checked against the group members list on initial authenticati | ||||||
|    --oidc-issuer-url=https://sts.windows.net/{tenant-id}/ |    --oidc-issuer-url=https://sts.windows.net/{tenant-id}/ | ||||||
| ``` | ``` | ||||||
| 
 | 
 | ||||||
| Note: When using the Azure Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the proxy_buffer_size in nginx or implementing the [redis session storage](sessions.md#redis-storage) should resolve this. | Note: When using the Azure Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the `proxy_buffer_size` in nginx or implementing the [redis session storage](sessions.md#redis-storage) should resolve this. | ||||||
| 
 | 
 | ||||||
| ### ADFS Auth Provider | ### ADFS Auth Provider | ||||||
| 
 | 
 | ||||||
|  | @ -234,12 +233,6 @@ For LinkedIn, the registration steps are: | ||||||
| 3.  Fill in the remaining required fields and Save. | 3.  Fill in the remaining required fields and Save. | ||||||
| 4.  Take note of the **Consumer Key / API Key** and **Consumer Secret / Secret Key** | 4.  Take note of the **Consumer Key / API Key** and **Consumer Secret / Secret Key** | ||||||
| 
 | 
 | ||||||
| ### Microsoft Azure AD Provider |  | ||||||
| 
 |  | ||||||
| For adding an application to the Microsoft Azure AD follow [these steps to add an application](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app). |  | ||||||
| 
 |  | ||||||
| Take note of your `TenantId` if applicable for your situation. The `TenantId` can be used to override the default `common` authorization server with a tenant specific server. |  | ||||||
| 
 |  | ||||||
| ### OpenID Connect Provider | ### OpenID Connect Provider | ||||||
| 
 | 
 | ||||||
| OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects. | OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects. | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue