Opiniones sobre Autenticación de usuarios: Identity-Aware Proxy

not working

AMIT D. · Se revisó hace 4 meses

Jhon Lord G. · Se revisó hace 4 meses

@go.thu 施. · Se revisó hace 4 meses

ROHIT K. · Se revisó hace 4 meses

2511EC010006- L. · Se revisó hace 4 meses

lab is not working

ONUR Ö. · Se revisó hace 4 meses

ok

A12-B3-51 K. · Se revisó hace 4 meses

@go.thu 鄭. · Se revisó hace 4 meses

V Saishivram G. · Se revisó hace 4 meses

RAHUL .. · Se revisó hace 4 meses

Overall Issue: The backend infrastructure for this lab works perfectly, but the Google Cloud Console UI is severely out of sync and the lab instructions are outdated regarding the OAuth configuration. I was only able to complete Task 1 by bypassing the Cloud Console entirely and using gcloud CLI commands. Specific Bugs & Outdated Instructions: Outdated "OAuth Consent Screen" Instructions: The lab manual instructs users to navigate to the "OAuth consent screen" and use a "Get Started" wizard. The Cloud Console has recently updated this to the "Google Auth Platform." The setup wizard is gone, requiring users to manually figure out how to set the User Type to "Internal" under the Audience tab and configure the Branding tab. The lab instructions need to be updated to reflect this new UI. Persistent "Failed to load IAP resources" Error: Even after successfully deploying the App Engine app (verified via gcloud app browse and the App Engine traffic dashboard) and correctly configuring the Google Auth Platform, the Identity-Aware Proxy dashboard completely breaks. It constantly displays a blue banner stating "Failed to load IAP resources" and refuses to populate the App Engine resource in the list. UI Caching/Desync Issues: Hard refreshing, clearing caches, and using Incognito mode did not resolve the IAP dashboard error. The UI simply refused to acknowledge the backend App Engine deployment. The Required Workaround: Because the IAP UI was completely broken, I had to use the following Cloud Shell commands to force the completion of Task 1 and get the grading system to recognize it: gcloud iap web enable --resource-type=app-engine gcloud iap web add-iam-policy-binding --resource-type=app-engine --member="user:[STUDENT_EMAIL]" --role="roles/iap.httpsResourceAccessor" Recommendation: Please update the instruction manual to reflect the new "Google Auth Platform" interface, and investigate the caching/sync delay between App Engine deployments and the IAP Security dashboard in the Qwiklabs environment.

A3_B2_28_KRISHNA J. · Se revisó hace 4 meses

@go.thu 許. · Se revisó hace 4 meses

@go.thu 詹. · Se revisó hace 4 meses

@go.thu 沈. · Se revisó hace 4 meses

Abhay P. · Se revisó hace 4 meses

Aaradhya S. · Se revisó hace 4 meses

@go.thu 穆. · Se revisó hace 4 meses

Sunitha Kumari M. · Se revisó hace 4 meses

Missing steps in Task 2, I tried a lot but no luck getting the app listed in the IAP....

Aditya A. · Se revisó hace 4 meses

Aaradhya S. · Se revisó hace 4 meses

Not possible to finish the lab due to an error to load IAP. Fortunately, I have found a solution in the comments by an other user

Guillaume N. · Se revisó hace 4 meses

Federico Alexandro C. · Se revisó hace 4 meses

Failed to load IAP resources

Sait Nuri U. · Se revisó hace 4 meses

Megha P. · Se revisó hace 4 meses

A5_B2_40_SANSKAR E. · Se revisó hace 4 meses