Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-19747

Google API key management

          Details

          • Type: Patch
          • Status: Won't Do
          • Priority: Major
          • Resolution: Won't Do
          • Affects Version/s: 4.6.24, 4.7.14
          • Fix Version/s: None
          • Component/s: Core CiviCRM
          • Labels:
          • Versioning Impact:
            Patch (backwards-compatible bug fixes)
          • Documentation Required?:
            User and Admin Doc
          • Funding Source:
            Needs Funding
          • Verified?:
            No

            Description

            The Google API key is now required for the Geocoding API (https://developers.google.com/places/web-service/search).

            CRM-18830 fixes the issue, but is incomplete:

            • if the Geolocation key is empty, but a Google map key is present, then use the Google Map key to perform the call
            • clarify the setup screen (/civicrm/admin/setting/mapping?reset=1) that the Google API key is now required, and include a link to the user documentation on how to create one
            • add a chapter in the user documentation to go through creating a Google key, securing it (ie. IP address or URL-based), and enabling the Geocoding and Places API for this key (I think these are disabled by default on new API keys).

              Attachments

                Activity

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    nganivet Nicolas Ganivet
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: