This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Add SSL client cert option to endpoint #498
Comments
We should allow for SHA256 fingerprint checks to save us a little memory and run cycle. |
bbangert
modified the milestones:
PUSHSVC-21: Dedicated Partner Endpoint,
PUSHSVC-0: quality
Jul 28, 2016
pjenvey
added a commit
that referenced
this issue
Sep 26, 2016
requires whitelisted TLS client certificates for connections to the endpoint except to health/log_check handlers closes #498
pjenvey
added a commit
that referenced
this issue
Sep 26, 2016
requires whitelisted TLS client certificates for connections to the endpoint except to health/log_check handlers closes #498
pjenvey
added a commit
that referenced
this issue
Sep 27, 2016
requires whitelisted TLS client certificates for connections to the endpoint except to health/log_check handlers closes #498
pjenvey
added a commit
that referenced
this issue
Sep 27, 2016
requires whitelisted TLS client certificates for connections to the endpoint except to health/log_check handlers closes #498
pjenvey
added a commit
that referenced
this issue
Sep 28, 2016
requires whitelisted TLS client certificates for connections to the endpoint except to health/log_check handlers closes #498
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our endpoint should have a separate config option to require SSL client certs, along with a config option to indicate acceptable SSL client certs.
The endpoint should include the domain for SSL client certs used in the push message logging.
The text was updated successfully, but these errors were encountered: