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 for additional authentication options [feature-request] #149

Open
cocowalla opened this issue Mar 27, 2020 · 0 comments
Open

Support for additional authentication options [feature-request] #149

cocowalla opened this issue Mar 27, 2020 · 0 comments

Comments

@cocowalla
Copy link

cocowalla commented Mar 27, 2020

At present, Function Monkey supports only token-based authentication. This is done through ITokenValidator.ValidateAsync(string authorizationHeader), so the validator only has the authorization available to it.

I'd like to use X.509 mutual TLS authentication. When using mutual TLS auth, Azure Functions makes the certificate available in a different header, X-ARR-ClientCert, as well as through HttpContext.Connection.ClientCertificate for the current request. I don't believe it's possible to achieve this today using ITokenValidator; you might be able to ignore the auth header in ValidateAsync and inject HttpContext into thhe validator, but feels a bit icky 😅

It would be useful to have a more "general purpose" authentication mechanism available, which perhaps had the full HttpContext available to it, by which I mean the "real" one, not the slimmed down FunctionMonkey.Abstractions.Contexts.HttpContext.

Love this project, BTW 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant