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

client authentication by public keys #106

Closed
simonsparks opened this issue May 31, 2016 · 3 comments
Closed

client authentication by public keys #106

simonsparks opened this issue May 31, 2016 · 3 comments
Labels

Comments

@simonsparks
Copy link

I am currently trying to set up a deployment on AWS where access to Fabio routes should be restricted to calls via AWS' API Gateway. For this I am aiming to verify a client certificate but as the docs state:

The API Gateway-generated SSL certificates are self-signed and only the public key of a certificate is visible in the API Gateway console or through the APIs.

so I don't appear to have access to the ca.crt to configure Fabio with. Is it possible to verify clients in Fabio by a list of keys rather than a ca certificate?

@magiconair
Copy link
Contributor

@simonsparks you only need the public key to enable client certificate authentication. In the example from fabio.properties this is path/to/clientauth.pem.

proxy.addr = :443;path/to/cert.pem;path/to/key.pem;path/to/clientauth.pem

However, I haven't tried this myself yet but it is the only option I have for configuring client certificate authentication. Please note that you still have to provide TLS certificates for the fabio listener itself since client cert authentication only works via SSL AFAIK.

Let me know how this works out for you. If you continue to have problems then I can try this myself.

@simonsparks
Copy link
Author

@magiconair Yes this did work for me; thanks for your response.
p.s. Really pleased with Fabio's capability on our platform, great work!

@magiconair
Copy link
Contributor

@simonsparks Glad to hear and happy that it works. Let me know if there are other issues.

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

No branches or pull requests

2 participants