git.iko.soy/typeable/oauth2-proxy
on master help sign in
Remove the information about `Microsoft Azure AD` in the provider documentation (#1477)
0e10fb8Ole-Martin Bratteng
CHANGELOG.md+2
compare with master
unifiedsplit
@@ -8,6 +8,8 @@
8
8
9## Changes since v7.2.1
9## Changes since v7.2.1
10
10
11+- [#1477](https://github.com/oauth2-proxy/oauth2-proxy/pull/1477) Remove provider documentation for `Microsoft Azure AD` (@omBratteng)
12+
11# V7.2.1
13# V7.2.1
12
14
13## Release Highlights
15## Release Highlights
docs/versioned_docs/version-7.2.x/configuration/auth.md+1−8
@@ -15,7 +15,6 @@ Valid providers are :
15- [Keycloak](#keycloak-auth-provider)
15- [Keycloak](#keycloak-auth-provider)
16- [GitLab](#gitlab-auth-provider)
16- [GitLab](#gitlab-auth-provider)
17- [LinkedIn](#linkedin-auth-provider)
17- [LinkedIn](#linkedin-auth-provider)
18−- [Microsoft Azure AD](#microsoft-azure-ad-provider)
19- [OpenID Connect](#openid-connect-provider)
18- [OpenID Connect](#openid-connect-provider)
20- [login.gov](#logingov-provider)
19- [login.gov](#logingov-provider)
21- [Nextcloud](#nextcloud-provider)
20- [Nextcloud](#nextcloud-provider)
@@ -87,7 +86,7 @@ Note: The user is checked against the group members list on initial authenticati
87 --oidc-issuer-url=https://sts.windows.net/{tenant-id}/
86 --oidc-issuer-url=https://sts.windows.net/{tenant-id}/
88```
87```
89
88
90−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.
89+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.
91
90
92### ADFS Auth Provider
91### ADFS Auth Provider
93
92
@@ -234,12 +233,6 @@ For LinkedIn, the registration steps are:
2343. Fill in the remaining required fields and Save.
2333. Fill in the remaining required fields and Save.
2354. Take note of the **Consumer Key / API Key** and **Consumer Secret / Secret Key**
2344. Take note of the **Consumer Key / API Key** and **Consumer Secret / Secret Key**
236
235
237−### Microsoft Azure AD Provider
238−
239−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).
240−
241−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.
242−
243### OpenID Connect Provider
236### OpenID Connect Provider
244
237
245OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects.
238OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects.