You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an application that uses the Google API for PlacesAPI, TimeZoneApi and GeoCodingAPI.
Now we have a GeoContext spring bean defined where we set the API key and the Enterprise credentials. Which we inject in our service to use for the calls to the api's
// Config class
builder.apiKey(googleApiKey);
builder.enterpriseCredentials(googleClientId, googleCryptoKey);
builder.channel(googleChannel);
// Call in the service
PlaceAutocompleteRequest request = PlacesApi.placeAutocomplete(context, query, googleSesionKey).language("en").await();
Whenever we do a call to the placesAPI then it builds the url like below with the client and signature instead of the apiKey
this gives us back an error stating that an api key must be provided.
During debugging of the placesApi I notice that it adds this clientid instead of APIKey when it is provided and because of a setting canuseclient is set to true.
Is this a bug that the placesapi config is wrong as it should not seem to use this clientid? I am also not sure where this can be modified to false.
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
We have an application that uses the Google API for PlacesAPI, TimeZoneApi and GeoCodingAPI.
Now we have a GeoContext spring bean defined where we set the API key and the Enterprise credentials. Which we inject in our service to use for the calls to the api's
Whenever we do a call to the placesAPI then it builds the url like below with the client and signature instead of the apiKey
https://maps.googleapis.com/maps/api/place/autocomplete/json?**client=XXXXXXX**&input=fa&types=%28cities%29&language=en&sessiontoken=bb1fb770-76ec-42da-b80b-7ab82dd74f23&**signature=XXXX**
this gives us back an error stating that an api key must be provided.
During debugging of the placesApi I notice that it adds this clientid instead of APIKey when it is provided and because of a setting canuseclient is set to true.
Is this a bug that the placesapi config is wrong as it should not seem to use this clientid? I am also not sure where this can be modified to false.
Thanks
The text was updated successfully, but these errors were encountered: