topic Re: Anybody else seeing Map View failures with vSZ-E 3.4.1.0.208? in SmartZone and Virtual SmartZone

Anybody else seeing Map View failures with vSZ-E 3.4.1.0.208?

stephen_thomas_ — Mon, 26 Dec 2016 05:51:00 GMT

We're new to Ruckus and have just deployed Virtual SmartZone - Essentials
3.4.1.0.208.

If I log onto the vSZ web interface via https://10.129.172.30:8443, Map View works correctly.

If I use https://ruckus-vsz.curric.lan:8443 instead (resolves to the same host), it doesn't; instead I get a brief flash of the working Maps screen, quickly replaced by

The JavaScript console shows that the last site fetched was https://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate, that no key= or client= parameter was supplied in the URL for that request, and that the message

Google Maps API error: MissingKeyMapError https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error

was logged straight afterwards.

Using the controller via https://10.129.172.30:8443 also performs the same request to https://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate (also with no key= or client= parameter) but no Maps API error is logged as a result and the Maps View works as it should.

It also works if I fiddle with our DNS a little and then get to the controller via https://ruckus:8443 or https://kitchen:8443. It's not just simple hostnames though - https://ruckus-vsz:8443 and https://kaboodle:8443 fail the same way as https://ruckus-vsz.curric.lan:8443 does.

My best guess at what's going on is that Ruckus is still relying on the grandfathering-in of keyless access to the Maps API, as documented here:

https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update

and that dotted-quad hostnames, "ruckus" and "kitchen" somehow pass Google's mysterious grandfather filter while none of the other hostnames I've tried do so.

So I'm just wondering if anybody else has seen this issue. If you have, or if you haven't but it interests you, could you share the hostname of your vSZ controller?

Re: Anybody else seeing Map View failures with vSZ-E 3.4.1.0.208?

stephen_thomas_ — Mon, 26 Dec 2016 10:39:02 GMT

Ruckus Support has just provided me with a patch file (ER-4350-3_4_1_0_208_API_key_v1_0.ksp) that has corrected this issue. Thanks to the support and dev teams for their quick response.

Re: Anybody else seeing Map View failures with vSZ-E 3.4.1.0.208?

michael_brado — Tue, 03 Jan 2017 21:27:14 GMT

Glad to hear TS was able to help you out. I did some research, that confirms your resolution.

Oops! Something went wrong. This page didn't load Google Maps correctly. See the JavaScript console for technical details.

The client ID/API key has become a mandatory attribute in API request due to the new policy of using Google MAP API on June, 2016.

Trying to open a MAP view can get a 500 Internal Server error.

Depending on the environment, if you can wait to upgrade to later versions of code, this is slated to be resolved in 3.5, 3.4.1, 3.4.0, 3.2.1, and 3.1.2.

If you can't upgrade due to old AP support, etc. then the ER-4350 .KSP will resolve the issue.