简体   繁体   English

GCP - 启用外部身份提供商

[英]GCP - Enabling External Identity Provider

Trying to add external provider (github) to authenticate user.尝试添加外部提供程序 (github) 来验证用户。 However, I am running in to following error during Google Cloud Identity Platform setting但是,我在 Google Cloud Identity Platform 设置期间遇到以下错误

There was an error in updating the GCIP settings.更新 GCIP 设置时出错。 You can return to your configuration and retry later您可以返回到您的配置并稍后重试

Create Cloud Run Instance step is successful.创建 Cloud Run 实例步骤成功。 Add Authorized Domain step is failure添加授权域步骤失败

It looks like server is responding with 400 status code for PATCH request看起来服务器正在响应 PATCH 请求的 400 状态代码

Request URL: https://iap.clients6.google.com/v1/projects/<project id>/iap_web/appengine-test-3-295108123:iapSettings?updateMask=iapSettings.accessSettings.gcipSettings.tenantIds,iapSettings.accessSettings.gcipSettings.loginPageUri&key=<apikey masked>
Request Method: PATCH
Status Code: 400 

UPDATE Identity Aware Proxy (IAP) is enabled on App Engine to protect static artifacts deployed on app engine (python runtime)更新Identity Aware Proxy (IAP) 在 App Engine 上启用,以保护部署在 App Engine 上的 static 工件(python 运行时)

I ran into the same issue and a workaround was using the "I'll provide my own" instead of the "Use an existing hosted sign-in page" option.我遇到了同样的问题,解决方法是使用“我将提供我自己的”而不是“使用现有的托管登录页面”选项。 We provided the Cloud Run URL still as the URL and it successfully deployed.我们提供的 Cloud Run URL 仍然是 URL 并成功部署。 When we went to edit the Authentication URL, it appears that in the background, the method updated to "Use an existing hosted sign-in page."当我们去编辑身份验证 URL 时,似乎在后台,方法更新为“使用现有的托管登录页面”。 To confirm, we switched back to IAM and then did the steps to configure external identities.为了确认,我们切换回 IAM,然后执行配置外部身份的步骤。 We used the "Use an existing hosted sign-in page" and it worked this time.我们使用了“使用现有的托管登录页面”并且这次有效。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM