You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDKs should be compatible with pinned certificates for connecting to the Parse Servers, allowing for faster, safer deployment, particularly in small or internal deployments.
We could add ParseClient::setOptions() to support certificate pinning out of the box for both cURL and stream clients. This would also support any of the many other features for cURL and stream context.
For those interested I added an example for public key pinning, cert fingerprint checking, peer verification in PHP and JavaScript (not really a thing in javascript but useful) using self signed certs #513
Activity
davidtavarez commentedon Nov 28, 2017
@montymxb @kingmatusevich is this issue closed?
montymxb commentedon Nov 29, 2017
@davidtavarez Nope, it is still open and still something we are happy to implement in the future; but no work has started on this yet.
dplewis commentedon Jul 19, 2019
Doesn't
ParseClient::setCAFilealready kinda does this? I can add a valid test for this.What other types of SSL/TLS check would be needed? (That would support both cURL and stream_context).
dplewis commentedon May 11, 2023
This can be achieved by creating your own HTTP client and pass in your SSL/TLS options
https://github.com/parse-community/parse-php-sdk#http-clients
We could add
ParseClient::setOptions()to support certificate pinning out of the box for both cURL and stream clients. This would also support any of the many other features for cURL and stream context.dplewis commentedon May 13, 2023
For those interested I added an example for public key pinning, cert fingerprint checking, peer verification in PHP and JavaScript (not really a thing in javascript but useful) using self signed certs #513