You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/proposals/external-auth-filter.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ This proposal aim to provider users of the Gateway API with a native form of Aut
13
13
## Goals
14
14
15
15
- Integrate with the [HTTPExternalAuthFilter](https://gateway-api.sigs.k8s.io/reference/spec/#httpexternalauthfilter) for HTTPRoute in the Gateway API
16
+
- Ensure this capability is available only when users enable experimental features in NGF
16
17
- Support only [HTTPAuthConfig](https://gateway-api.sigs.k8s.io/reference/spec/#httpauthconfig)
17
18
- Provide users with a helm chart to deploy, manage and configure NGINX for Authentication use cases. i.e. the External Service
18
19
- Allow users to configure an exteranl IdP such as Keycloak or AzureAD
@@ -23,9 +24,11 @@ This proposal aim to provider users of the Gateway API with a native form of Aut
23
24
24
25
## Introduction
25
26
26
-
This document focus on an approach to have NGF integate with the HTTPExternalAuthFilter in the Gateway APi.
27
+
This document focus on an approach to have NGF integate with the HTTPExternalAuthFilter in the Gateway API.
27
28
This filter defines a mean to communicate with an external authentication services that can be responsible for both Authenticaiton and Authroization of requests to a backend application.
28
29
30
+
> ⚠️ This filter is currently part of the Gateway API experimental channel. The API is subject to changes that may break implementations.
31
+
29
32
## API, Customer Driven Interfaces, and User Experience
0 commit comments