Status Update
No update yet.
Comments
mc...@google.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
[Deleted User] <[Deleted User]>
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:
cs...@google.com
Here are several sources that can be used to help you split the root.pem file into 1 file per certificate, if required by your tooling and software environment:
-
-
-
As an immediate fix to get your Google Maps Platform requests working again, the main certificate to install is the "GTS Root R1" certificate, which begins at line 896 in the current roots.pem file. Please note that this issue may reoccur in the future if you don't install all the certificates.
[Deleted User] <[Deleted User]>
To help customers using Java or Mozilla NSS, we have updated the Java keytool and NSS certutil sections in our
Description
when clicking on the map, we have code that shows a map with tool tips in a popup.
Up until about 2 releases of chrome ago, it worked fine, but now in both Chrome 45.0.2454.101 (64-bit) and Chrome Canary 47.0.2521.0 canary (64-bit) the tiles do not show. There are no JS errors on the page,
On every other browser this still works fine.
There have been no source code changes at our end, I think this coincides iwht the september 15th release of 3.22 of the api