Skip to content
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

support logical OR (vs logical AND) for multiple auth mechanisms #3207

Closed
bdecoste opened this issue Jun 23, 2020 · 4 comments
Closed

support logical OR (vs logical AND) for multiple auth mechanisms #3207

bdecoste opened this issue Jun 23, 2020 · 4 comments
Labels
Enterprise Issue is released in Enterprise Gloo only Type: Enhancement New feature or request

Comments

@bdecoste
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I'd like to provide multiple auth mechanisms where a logical OR will pass the request. Currently Gloo only supports logical AND for multiple auth mechanisms

Describe the solution you'd like
Support logical OR for multiple auth mechanisms

@bdecoste bdecoste added Type: Enhancement New feature or request Enterprise Issue is released in Enterprise Gloo only labels Jun 23, 2020
@bdecoste
Copy link
Contributor Author

This includes logical ORs between JWT, multiple Basic Auth (i.e. multiple passwords configured in an authconfig), and multiple extauth protocols (e.g. Basic Auth OR API Key).

@lgadban
Copy link
Contributor

lgadban commented Oct 15, 2020

@kdorosh just a heads up that the existing API docs for this feature are not rendering correctly:
https://docs.solo.io/gloo/latest/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/extauth/v1/extauth.proto.sk/#authconfig

How to handle processing of named configs within an auth config chain. An example config might be: ( basic1

@kdorosh
Copy link
Contributor

kdorosh commented Oct 16, 2020

looked into it briefly, appears to be a solokit bug 💢

doc should be fixed now

@saiskee
Copy link
Contributor

saiskee commented Jan 20, 2021

Fix has been implemented and backported to 1.6; closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enterprise Issue is released in Enterprise Gloo only Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants