Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

Commit

Permalink
EVEREST-107 remove authentication limitations from README
Browse files Browse the repository at this point in the history
  • Loading branch information
recharte committed Feb 20, 2024
1 parent 3a91d3c commit 12914d3
Showing 1 changed file with 0 additions and 12 deletions.
12 changes: 0 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,15 +47,3 @@ Once provisioning is complete, you can expose your everest installation using th
You can visit http://127.0.0.1:8080 to create your first database cluster!
## Known limitations
- There are no authentication or access control features, but you can integrate Everest with your existing solution.
* [Ambassador](https://github.com/datawire/ambassador) via
[auth service](https://www.getambassador.io/reference/services/auth-service)
* [Envoy](https://www.envoyproxy.io) via the
[External Authorization HTTP Filter](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ext_authz_filter.html)
* AWS API Gateway via
[Custom Authorizers](https://aws.amazon.com/de/blogs/compute/introducing-custom-authorizers-in-amazon-api-gateway/)
* [Nginx](https://www.nginx.com) via
[Authentication Based on Subrequest Result](https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/)

0 comments on commit 12914d3

Please sign in to comment.