wn/traefik-forward-auth
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Modify references from Universal Authentication to Global Authentication

Browse Source
This commit is contained in:
Thom Seddon 2020-05-07 15:22:48 +01:00
parent 1ac0ca9732
commit 07f9587bc1
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -28,7 +28,7 @@ A minimal forward authentication service that provides OAuth/SSO login and authe
- [Forwarded Headers](#forwarded-headers)
- [User Restriction](#user-restriction)
- [Applying Authentication](#applying-authentication)
- [Universal Authentication](#universal-authentication)
- [Global Authentication](#global-authentication)
- [Individual Ingress Authentication in Kubernetes](#individual-ingress-authentication-in-kubernetes)
- [Individual Container Authentication in Swarm](#individual-container-authentication-in-swarm)
- [Rules Based Authentication](#rules-based-authentication)
@ -328,9 +328,9 @@ The authenticated user is set in the `X-Forwarded-User` header, to pass this on
### Applying Authentication
Authentication can be applied in a variety of ways, either universally across all requests, or to individual containers/ingresses.
Authentication can be applied in a variety of ways, either globally across all requests, or to individual containers/ingresses.
#### Universal Authentication
#### Global Authentication
This can be achieved by enabling forward authentication for an entire entrypoint, for example, with http only:
@ -411,7 +411,7 @@ See the examples directory for more examples.
#### Rules Based Authentication
You can also leverage the `rules` config to selectively apply authentication via traefik-forward-auth. For example if you enabled universal authentication by enabling forward authentication for an entire entrypoint, you can still exclude some patterns from requiring authentication:
You can also leverage the `rules` config to selectively apply authentication via traefik-forward-auth. For example if you enabled global authentication by enabling forward authentication for an entire entrypoint, you can still exclude some patterns from requiring authentication:
```
# Allow requests to 'dash.example.com'

2
examples/traefik-v1.7/kubernetes/advanced-single-pod/README.md
View File

@ -3,7 +3,7 @@
This is an advanced example of how to deploy traefik and traefik-forward-auth in a single pod. This example is a good starting point for those who already have a manually defined traefik config (e.g. not using helm).
This example uses [Universal Authentication](https://github.com/thomseddon/traefik-forward-auth/blob/master/README.md#universal-authentication) to apply authentication for the entire `https` entrypoint.
This example uses [Global Authentication](https://github.com/thomseddon/traefik-forward-auth/blob/master/README.md#global-authentication) to apply authentication for the entire `https` entrypoint.
This example also includes SSL via traefik acme/lesencrypt, auth host mode, exposes the traefik dashboard and leverages kustomise. No special config if required for your applications, but a simple example "whoami" application (deployment, service and ingress) is included for completeness.