Google 的用戶端 ID 和用戶端密鑰:
您必須為 Google 指派用戶端 ID, OAuth 2.0 要求將使用這個 ID 給
識別要求的來源與用戶端密鑰,可用來防止
而非偽造要求Google 用戶端 ID 和用戶端密鑰可以是任何網址安全
字串值。您必須確保用戶端密鑰為
只有 Google 和你的服務看得到。
選用的範圍字串。
視 API 提供的使用者資料數量和種類而定
建議您定義代表不同使用者類別的範圍
資料。如此一來,雙方只能向使用者要求存取權
將資料提供給用戶端
以及已取得授權的範圍尤其是您的服務提供更多可用資料時
,您可以使用範圍
只能存取部分資料
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2024-10-09 (世界標準時間)。"],[[["Before integrating with Google services (excluding Google Assistant), gather necessary information like authorization and token endpoint URLs and contact your developer relations representative."],["You need to provide Google with a client ID and secret, which can be any URL-safe string, and ensure the client secret remains confidential."],["When setting up your authorization endpoint, allowlist the provided `redirect_uri` for Google's client ID."],["Optionally, you can enhance security by implementing a token revocation endpoint, Cross-Account Protection, and defining scopes to limit data access for Google."],["To initiate the process, locate your Google API Project ID within the Google API Console."]]],[]]