diff options
| author | mo khan <mo@mokhan.ca> | 2025-05-26 17:07:14 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-05-26 17:07:14 -0600 |
| commit | d5933faef4b4b773e053a2e11bf3131dac407500 (patch) | |
| tree | bb889e18999f50f639fab4963e8c7fd8d9267720 /share | |
| parent | 3367610c7878707e641d068b1f889209f236e54c (diff) | |
docs: add a summary
Diffstat (limited to 'share')
| -rw-r--r-- | share/man/ENVOY.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/share/man/ENVOY.md b/share/man/ENVOY.md index 3f11f9e..1dd8953 100644 --- a/share/man/ENVOY.md +++ b/share/man/ENVOY.md @@ -613,6 +613,22 @@ cd "$(dirname "$0")/.." ./bin/sparkled # launch sparkled in foreground ``` +## Summary + +Envoy provides a lot of features out of the box making it possible for +application developers to focus on their core domain. This makes it easier to +offload complex and error prone duties such as interacting with an OIDC Provider +and managing key material like an OAuth Client Secret a non-event. By moving +these responsibilities into Envoy we reduce the opportunity for tokens to get +leaked and we ensure that we adhere to open standards while also creating safe +extension points for extending authorization decisions. Envoy's ability to +modify incoming and outgoing requests before delivery makes it possible to +remove sensitive headers and/or convert them to a canonical representation in a +single consistent way. Envoy can handle mapping Authorization headers, session +cookies, query string parameters into a single consistent interface making it +possible to reduce the need for each application to handle each +authentication/authorization strategy that GitLab as a whole supports. + ## References * [Envoy Proxy](https://www.envoyproxy.io/) |
