Developing Applications on Google Cloud: Adding User Authentication and Intelligence to Your Application Ulasan

ANJALI K. · Diulas 11 hari lalu

Payal N. · Diulas 11 hari lalu

sharu s. · Diulas 11 hari lalu

Bhagyashree P. · Diulas 11 hari lalu

Uche N. · Diulas 11 hari lalu

Abhin R. · Diulas 12 hari lalu

Alex K. · Diulas 12 hari lalu

Etwari K. · Diulas 12 hari lalu

Kendall L. · Diulas 12 hari lalu

Lalit K. · Diulas 12 hari lalu

Payal N. · Diulas 12 hari lalu

Sonu K. · Diulas 12 hari lalu

Julian B. · Diulas 12 hari lalu

Siva Ganesh M. · Diulas 12 hari lalu

Good

madhusudhan G. · Diulas 12 hari lalu

Siva Ganesh M. · Diulas 12 hari lalu

Susmitha S. · Diulas 12 hari lalu

the instruction is not clear worst instruction set .

Rupal R. · Diulas 12 hari lalu

Shubham K. · Diulas 12 hari lalu

MD Naushad A. · Diulas 13 hari lalu

There were a whole lot of code changes to enable OAuth2 login that didn't have their goal explained upfront. Session management, callback handling, and auth guarding were all added at the same time in huge swaths of code copied in without giving an understanding of what OAuth step is being handled by each piece of code. After client setup, I would've liked to see auth guarding, callback handling, and then session management as separate tasks in that order. Each task would need to have a quick login testing phase to help show/explain which step of the OAuth2 flow you have made functional. Otherwise, I'm just learning how to copy-paste code fast, without gaining understanding of the OAuth2 flow as it pertains to my sample application.

Travis I. · Diulas 13 hari lalu

Pruthviraj W. · Diulas 13 hari lalu

sammy d. · Diulas 13 hari lalu

Hector Eduardo R. · Diulas 13 hari lalu

VENNAPUSA N. · Diulas 13 hari lalu