Fixed
Status Update
Comments
na...@google.com <na...@google.com> #2
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
he...@gmail.com <he...@gmail.com> #3
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:
na...@google.com <na...@google.com>
st...@google.com <st...@google.com> #4
Please note that many tools will only display and/or import the first certificate from https://pki.goog/roots.pem , which will not be sufficient to fix this situation.
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:
-https://developers.google.com/maps/root-ca-faq#how_do_i_extract_individual_certificates_from_rootspem
-https://geeklah.com/working_with_pem_files.html
-https://stackoverflow.com/questions/14660767/keytool-importing-multiple-certificates-in-single-file
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.
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.
Description
Hi guys,
The StreetviewService getPanoramaByLocation(latlng, radius, cbk) function fails when the 'radius' argument is not an integer...
You can check the following jsfiddle where the issue is obvious :
Probably a '.' encoding issue ? (it appears as '.' in the request URL, not %2E). Anyway, rounding the value is probably enough - but this should not be let to the API user :-)
Thanks !