Fixed
Status Update
No update yet.
Comments
aa...@gmail.com
This is to confirm that we plan to resume the rollout of the new cross-signed root CA certificate as described in
The rollout will be very gradual, with incremental launches across the Google Maps Platform services and regions, and its phases will proceed depending on engineering evaluations rather than by a defined timetable. The change will be transparent to the vast majority of Google Maps Platform API clients, including all mainstream maintained OS versions.
For more information, please see the FAQ resources listed in
ju...@google.com
ju...@google.com
We have been made aware of several customer issues in the past few days with SSL/TLS due to this rollout having resumed.
At this stage, the best course of action is to ensure that your client TLS stack can dynamically work with intermediary certificates signed by any of the (~40) root CAs fromhttps://pki.goog/roots.pem .
In other words, the root CA signing intermediary certificates for requests tohttps://maps.googleapis.com/* cannot be assumed to be static, nor can the set of root CAs be expected not to change before they expire.
We have published FAQs at the following addresses:https://pki.goog/faq/ is more high-level, and https://developers.google.com/maps/root-ca-faq is more technical.
At this stage, the best course of action is to ensure that your client TLS stack can dynamically work with intermediary certificates signed by any of the (~40) root CAs from
In other words, the root CA signing intermediary certificates for requests to
We have published FAQs at the following addresses:
Description