Fixed
Status Update
No update yet.
Comments
pa...@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
p....@gmail.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:
ev...@gmail.com
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.
eb...@gmail.com
To help customers using Java or Mozilla NSS, we have updated the Java keytool and NSS certutil sections in our
dr...@gmail.com
Dear developers, the new GTS Root R1 Cross certificates have now fully rolled out to all Google Maps Platform services.
tr...@gtempaccount.com
We are also delaying migrating to v3 until this feature is implemented.
ka...@gmail.com
same here. correct me if I'm wrong but you (google team) were planning on
implementing support for custom maps from the beginning, as it's one of the main map
class functionalities of v2.x and you said, you are going to implement all of v2.x
functionalities. so it is just a question of time, isn't?
implementing support for custom maps from the beginning, as it's one of the main map
class functionalities of v2.x and you said, you are going to implement all of v2.x
functionalities. so it is just a question of time, isn't?
ma...@gmail.com
waiting here, too
guess those requests concern same topic
http://code.google.com/p/gmaps-api-issues/issues/detail?id=1831&q=label%3AApiType-Javascript3&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal
and
http://code.google.com/p/gmaps-api-issues/issues/detail?id=1402&q=label%3AApiType-Javascript3&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal
merging them together probably will rate it higher (34 stars)? ;)
guess those requests concern same topic
and
merging them together probably will rate it higher (34 stars)? ;)
cm...@googlemail.com
I'm looking forward to this change as well, because we need this for our project and
I like the v3 API so far except that missing feature.
I like the v3 API so far except that missing feature.
sa...@gmail.com
Waiting for some word on this too. (Started redundant feature request 1930 when I
didn't find this thread sooner.) GTileLayerOverlay is supported as a Mapserver
output method since 5.2 and it is very fast in API v2 with caching. We really need
this in API v3 ASAP!!
There must be a major issue with this or we would have heard something by now. I
think maybe this is a fundamental bandwidth issue with mobile devices trying to load
all the tiles a desktop would at full size and trying to scale down in the client
device to small screens (s-l-o-w)? Maybe there needs to be a resolution control
implemented at the server.
didn't find this thread sooner.) GTileLayerOverlay is supported as a Mapserver
output method since 5.2 and it is very fast in API v2 with caching. We really need
this in API v3 ASAP!!
There must be a major issue with this or we would have heard something by now. I
think maybe this is a fundamental bandwidth issue with mobile devices trying to load
all the tiles a desktop would at full size and trying to scale down in the client
device to small screens (s-l-o-w)? Maybe there needs to be a resolution control
implemented at the server.
ra...@gmail.com
I have added some "Sparse Tile Layer Overlay" examples:
http://www.polyarc.us/sparse
http://www.polyarc.us/road
http://www.polyarc.us/rail
The "height" & "width" & "bbox" values expected by mapserver are available to the
"setUrl" method. The traditional "x" & "y" & "z" tile values are also available to
the "setUrl" method.
xy.x = tile X offset
xy.y = tile Y offset
xy.X = tile width
xy.Y = tile height
xy.x0 = begin longitude
xy.y0 = begin latitude
xy.x1 = end longitude
xy.y1 = end latitude
A single "Sparse Tile Layer Overlay" can handle multiple tile sets without redundant
OverlayViews, each requiring its own event listeners.
The "height" & "width" & "bbox" values expected by mapserver are available to the
"setUrl" method. The traditional "x" & "y" & "z" tile values are also available to
the "setUrl" method.
xy.x = tile X offset
xy.y = tile Y offset
xy.X = tile width
xy.Y = tile height
xy.x0 = begin longitude
xy.y0 = begin latitude
xy.x1 = end longitude
xy.y1 = end latitude
A single "Sparse Tile Layer Overlay" can handle multiple tile sets without redundant
OverlayViews, each requiring its own event listeners.
Description
In v2, it's possible to create a custom map type by implementing a custom
getTileUrl method of GTileLayer object.
I'm not suggesting for "duplicating" the way v2 works in v3, but I think v3
should have it's own feature to help developers create their own custom map
types.