- 最新
- 投票最多
- 评论最多
Hello!
While I'm unable to speak authoritatively regarding the Google Cloud side of this configuration, it does seem like the Client Secret value may be an issue here. Setting up an API Destination Connection utilizing Oauth authorization does require the use of a client ID and a client secret. Looking through the Google Cloud documentation and doing some testing in the Google Cloud console (which again, I am unfamiliar with), I was only able to find that setting up an Oauth 2.0 Client ID as a Web Application type provided me with credentials that included both a client ID and client secret. However, when specifying these as in my API Destination Connection and specifying the Oauth HTTP Parameters found in the Oauth JSON file from Google Cloud, and utilizing "https://oauth2.googleapis.com/token" as the Authorization endpoint, the Connection still indicates a Deauthorized error with message "The partner authorization grant type is not supported by the partner authorization server."
It may be necessary to reach out to Google Cloud support for more information on how best to configure the API Authorization Endpoint and Client Credentials in Google Cloud to then be used when setting up the connection in EventBridge API Destinations.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 7 个月前