Autenticação de usuário: Identity-Aware Proxy avaliações
236189 avaliações
terrible, it doesn't work
Marco L. · Revisado há about 2 months
Mamidi v. · Revisado há about 2 months
Isn't working, I can't continue after the disable the Flex API step.
Graciela C. · Revisado há about 2 months
Deepikap P. · Revisado há about 2 months
mai iap is unable to load resourses
PARI M. · Revisado há about 2 months
During the lab, the Identity-Aware Proxy page continuously showed the error "Failed to load IAP resources" and did not list the App Engine application. Because of this, it was impossible to enable IAP through the console as instructed in the lab steps. The App Engine service was deployed correctly and accessible, but the IAP interface did not load the resources. I had to enable IAP via gcloud CLI instead, which allowed the application to be protected and accessible. However, the lab verification did not recognize the completion because the action was not performed through the console. This appears to be an issue with the IAP resource loading in the lab environment. I tried 3 times and nothing.
Talita G. · Revisado há about 2 months
not working
AMIT D. · Revisado há about 2 months
Jhon Lord G. · Revisado há about 2 months
@go.thu 施. · Revisado há about 2 months
ROHIT K. · Revisado há about 2 months
2511EC010006- L. · Revisado há about 2 months
lab is not working
ONUR Ö. · Revisado há about 2 months
ok
A12-B3-51 K. · Revisado há about 2 months
@go.thu 鄭. · Revisado há about 2 months
V Saishivram G. · Revisado há about 2 months
RAHUL .. · Revisado há about 2 months
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. · Revisado há about 2 months
@go.thu 許. · Revisado há about 2 months
@go.thu 詹. · Revisado há about 2 months
@go.thu 沈. · Revisado há about 2 months
Abhay P. · Revisado há about 2 months
Aaradhya S. · Revisado há about 2 months
@go.thu 穆. · Revisado há about 2 months
Sunitha Kumari M. · Revisado há about 2 months
Missing steps in Task 2, I tried a lot but no luck getting the app listed in the IAP....
Aditya A. · Revisado há about 2 months
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.