서드 파티가 자신의 웹사이트에서 내 클라이언트 ID를 사용하지 못하도록 하기 위해 내 클라이언트 ID는 내가 구체적으로 승인한 URL 목록에만 사용할 수 있습니다.
Cloud 콘솔에서 클라이언트 ID 찾기
Cloud 콘솔에서의 URL 승인
승인된 URL은 모두 클라이언트 ID 페이지의 클라이언트 ID gme-[company]의 승인된 URL 표에 표시됩니다.
URL을 삭제하려면 URL 왼쪽에 있는 체크박스를 선택하고 표 오른쪽 상단에 있는 delete삭제 아이콘을 클릭합니다.
새 URL을 추가하려면 표 하단에 있는 URL 추가를 클릭합니다.
중요: 승인된 클라이언트 ID URL의 규칙은 API 키 리퍼러 제한사항과 다릅니다. 자세한 내용은 아래를 참고하세요.
승인된 URL과 관련하여 아래 사항을 고려하세요.
도메인 이름이나 IP 주소는 공개적으로 액세스가 가능하지 않아도 됩니다.
예를 들어 http://myintranet 및 http://192.168.1.1은 사용할 수 있습니다.
지정된 도메인의 모든 하위 도메인도 승인됩니다.
예를 들어 네이키드 도메인 http://example.com이 승인되면 하위 도메인 http://www.example.com도 승인됩니다. 그 반대는 해당하지 않습니다. 즉, http://www.example.com이 승인된다고 http://example.com이 자동으로 승인되는 것은 아닙니다.
승인된 경로의 모든 하위 경로도 승인됩니다.
예를 들어 http://example.com이 승인되면 http://example.com/foo도 승인됩니다. 또한 지정된 도메인의 하위 도메인도 승인되므로 http://sub.example.com/bar가 승인됩니다.
경로는 대소문자를 구분합니다.
예를 들어 http://www.example.com/ThisPath/는 http://www.example.com/thispath/와 다릅니다.
유효한 URL을 특정 포트를 사용하는 URL로만 제한할 수 있습니다.
예를 들어 http://example.com:8080/foo가 지정되면 http://example.com이 승인되지 않습니다.
HTTP 프로토콜과 HTTPS 프로토콜은 서로 다른 URL로 간주됩니다.
예를 들어 https://example.com을 승인해도 http://example.com이 자동으로 승인되지 않습니다.
프로토콜 스킴 없이 서픽스 참조를 제공하면(예: www.example.com) HTTP와 HTTPS에 대해 각각 별도의 규칙이 생성됩니다.
HTTP 또는 HTTPS 이외의 다른 프로토콜 스킴은 Cloud 콘솔에서 제공되는 안내를 참고하세요.
[null,null,["최종 업데이트: 2023-09-14(UTC)"],[[["\u003cp\u003eThe Google Maps Platform Premium Plan is no longer available for new users and this documentation is for existing legacy applications using client IDs.\u003c/p\u003e\n"],["\u003cp\u003eFor new applications, always use API keys instead of client IDs for authentication.\u003c/p\u003e\n"],["\u003cp\u003eClient ID usage is restricted to authorized URLs which can be managed in the Google Cloud Console.\u003c/p\u003e\n"],["\u003cp\u003eAuthorizing a domain automatically authorizes all its subdomains and subpaths, differing from API key referrer restrictions.\u003c/p\u003e\n"],["\u003cp\u003eHTTP and HTTPS protocols are treated as separate URLs for authorization purposes, unlike API key referrer restrictions.\u003c/p\u003e\n"]]],[],null,["# Client ID URL Authorization\n\n**Important:** The Google Maps Platform Premium Plan is no longer available for\nsign up or new customers.\n| **Caution:** This document is only provided as a reference for maintaining existing legacy applications that use client IDs. For new applications, *always* use API keys! See the [Premium Plan Authentication Overview](/maps/premium/authentication/overview) for further details.\n\nMaps JavaScript API client ID authentication\n--------------------------------------------\n\nYou can authenticate your requests with the Google Maps Platform using a client ID\nin combination with **URL registration** (instead of an API key).\n\n### Specify a client ID when loading the API\n\n| **Warning:** Requests containing both a client ID and an API key may result in unexpected API behavior or unintended billing behavior. To prevent this, make sure your requests use only one of these parameters.\n\nThe code below shows you how to replace \u003cvar translate=\"no\"\u003eYOUR_CLIENT_ID\u003c/var\u003e\nwith your own client ID when loading the Google Maps Platform. \n\n \u003cscript async defer src=\"https://maps.googleapis.com/maps/api/js?client=\u003cvar translate=\"no\"\u003eYOUR_CLIENT_ID\u003c/var\u003e&v=quarterly&callback=initMap\"\u003e\u003c/script\u003e\n\n### Manage authorized URLs\n\nTo prevent a third party from using your client ID on their own website, the\nuse of your client ID is restricted to a list of URLs that you have specifically\nauthorized.\n\n#### Locate your client ID in the Cloud console\n\n| **Note:** If you are unable to locate the project linked to your client ID, see [Finding client ID project](/maps/premium/authentication/overview#finding-client-id-project) and [Pausing your client ID](/maps/premium/authentication/overview#pause-client-id).\n\n#### URL authorization in the Cloud console\n\n- Your authorized URLs are all listed in the\n **Authorized URLs for Client ID gme-\\[company\\]** table on the\n [Client ID page](https://console.cloud.google.com/project/_/google/maps-apis/clientid).\n\n- To remove a URL, check the box to the left of the URL and click the\n delete **delete** icon at the top right\n of the table.\n\n- To add new URLs, click **Add URLs** at the bottom of the table.\n\nInportant: The rules of authorized client IDs URLs differs from API key referrer\nrestrictions. See below for further details.\n\nThe following considerations apply regarding URLs that are authorized:\n\nThe domain name or IP address does not have to be publicly accessible.\n: For example, `http://myintranet` and `http://192.168.1.1` are valid entries.\n\nAll subdomains of a specified domain are also authorized.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if the naked domain `http://example.com` is authorized, then\n subdomain `http://www.example.com` is also authorized. The reverse\n is not true: if `http://www.example.com` is authorized, `http://example.com`\n is not automatically authorized.\n\nAll subpaths of an authorized path are also authorized.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if `http://example.com` is authorized, then\n `http://example.com/foo` is also authorized. In addition, because subdomains\n of a specified domain are also authorized, `http://sub.example.com/bar` is\n authorized.\n\nPaths are case sensitive.\n\n: For example, `http://www.example.com/ThisPath/` is not the same as\n `http://www.example.com/thispath/`.\n\nYou may restrict valid URLs to those using certain ports.\n\n: For example, if `http://example.com:8080/foo` is specified,\n that doesn't authorize `http://example.com`.\n\nHTTP and HTTPS protocols are considered different URLs.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if `https://example.com` is authorized, `http://example.com` is\n not automatically authorized.\n\n If you provide a suffix reference without protocol scheme, for example\n `www.example.com`, separate rules will be created both for HTTP and HTTPS.\n\nFor more exotic protocol schemes than HTTP or HTTPS, see the provided\ninstructions in the Cloud console."]]
