You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
Rather than trying to define access policies within argo config itself (#32), would it be possible to at least say that hey this particular service can only be accessed through Cloudflare access, and reject all unauthenticated traffic?
@mattalberts i saw #32 and it seems to suggest a greater scope where access policies can be defined via argo config. This issue represents a much smaller scope one of ensuring traffic is going through access, rather than defining the policies. Does that distinction make sense?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rather than trying to define access policies within argo config itself (#32), would it be possible to at least say that hey this particular service can only be accessed through Cloudflare access, and reject all unauthenticated traffic?
I imagine it's possible to set up a reverse proxy in between argo and the service being served and perform JWT verification (https://developers.cloudflare.com/access/setting-up-access/validate-jwt-tokens/), however that's a bunch of extra work.
The text was updated successfully, but these errors were encountered: