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

EVEREST-107 remove authentication limitations from README #458

Closed
wants to merge 1 commit into from
Closed

EVEREST-107 remove authentication limitations from README #458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions README.md
View file
Open in desktop
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/)
Loading