Integrate with Traefik, Nginx, Ambassador, Envoy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 415
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I'd like to use Ory Oathkeeper with:
- Traefik Forward Auth: (example)
- Implementation is required
- Document set up (with example config) in
Oathkeeper -> Scenarios (new section!) ->Nginx ForwardAuth
- Nginx Subrequest:
- Implementation should already work with the existing decisions endpoint
- Document set up (with example config) in
Oathkeeper -> Scenarios (new section!) ->Nginx ForwardAuth
- Ambassador Ambassador AuthService Plugin:
- Implementation should already work with the existing decisions endpoint
- Document set up (with example config) in
Oathkeeper -> Scenarios (new section!) ->Ambassador AuthService Plugin
- Envoy External Authorization
- Research is needed to decide if a custom endpoint is required or not
- Document set up (with example config) in
Oathkeeper -> Scenarios (new section!) -> Envoy External Authorization
Additional info
As per my comment https://github.com/ory/oathkeeper/pull/265#issuecomment-534967157 we would like to offer one endpoint per service:
/decisions/generic/...(this is currently/decisions)/decisions/traefik/...- ...
For backwards compatibility ideas see https://github.com/ory/oathkeeper/pull/265/files#r329310302
For implementation ideas see this PR: https://github.com/ory/oathkeeper/pull/265
Context
See comment https://github.com/ory/oathkeeper/issues/263#issuecomment-605912334
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review PR 265 and Oathkeeper’s existing /decisions endpoint first, then compare the listed Traefik, Nginx, Ambassador, and Envoy integration requirements. Done means the required service-specific integration behavior is defined or implemented and setup examples are documented under docs/oathkeeper in the proposed Scenarios sections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- api, backend, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100