-
Notifications
You must be signed in to change notification settings - Fork 4
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 authenticating on OU or CN #4
Comments
/cc @spheromak @kibra |
@joemiller I wonder what the default expectation is. Would you expect having specified both for it to be a default OR ? I think implementation wise the field should be an iota
spun up the quick example in playground: |
@kibra I think you already implemented something that accomplishes a similar goal? |
I believe I thought about it, but did not implement anything. Allowing the user to provide a validator function that accepts a request and context would provide this functionality. |
i'm thinking about adding an 'evaluator' (or better name?) to go-certauth. Use case is "allow any cert with OU=foo or CN=blah".
eg:
^^ current code, requires both OU and CN to match.
maybe something like:
"Or", "And" ..
The text was updated successfully, but these errors were encountered: