-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application level auth token verification on Seldon Core #1562
Comments
Issues go stale after 30d of inactivity. |
/remove-lifecycle stale |
I have been exploring this for quite some time and now started working on an example for clusters with istio enabled https://github.com/SachinVarghese/seldon-core/blob/auth/examples/auth/README.md |
This is great. Can you create a PR? |
Closing. Please reopen if we still need this or not done by @SachinVarghese PRs |
This issue aims to explore the advantages / disadvantages of adding application level auth token verification with standard OICD provider options, with the objective of verifying or rejecting requests that have a token that is not valid. Currently the best practice and suggested authentication implementation is by ensuring the cluster has ingress-level authentication, so the token is actually validated on the ingress, instead to having it on an application-level.
The text was updated successfully, but these errors were encountered: