Add the option to use OTP generator (like Google Authenticator ) for Identity Platform [154359804]

Assigned

Feature Request

Status Update

No update yet.

Description

aa...@google.com

created issue #1

Apr 18, 2020 02:03AM

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

As per the documentation[1], Identity Platform is providing the new feature to secure the users in the apps with SMS Multi-factor authentication. But, the customer wants to add the option to use Google Authenticator to manage multiple two-factor authentication keys.

[1]

https://cloud.google.com/blog/products/identity-security/protect-users-in-your-apps-with-multi-factor-authentication

How this might work:

If applicable, reasons why alternative solutions are not sufficient:

Other information (workarounds you have tried, documentation consulted, etc):

Comments

aa...@google.com <aa...@google.com> Apr 18, 2020 02:05AM

Assigned to gc...@google.com.

sa...@google.com <sa...@google.com> #2Apr 21, 2020 02:01AM

Hello,

Thanks for reaching out to us!

The Product Engineering Team has been made aware of your feature request, and will address it in due course. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.

In case you want to report a new issue, please do not hesitate to create a new [Issue Tracker] 1 thread describing your issue. Once again, thank you for the suggestions.

Thanks and Regards,
Onkar Mhetre
Google Cloud Support

ja...@fareclock.com <ja...@fareclock.com> #3Jul 21, 2020 01:45PM

Specifically, this happened to us. We have a GKE cluster with two similarly-sized node pools. One has E2 nodes and the other has C2D nodes. We wanted to temporarily double the size of our E2 nodepool and checked the quotas page first. The only quota in the entire GCP project that was above 20% was "CPUs" at 55%. We reasoned that since only half of our machines were in the nodepool we wanted to double, this would only raise us to around 80-85% of quota, which seemed safe for a temporary change. We were surprised to see our scale-up fail due to quota. (And then we clumsily tried to quickly scale down to get below quota using direct GCE ASG scaling rather than GKE autoscaler, which ended up deleting a bunch of our more active machines instead of the empty ones — perhaps user error, but a bigger impact than we had expected for what we thought was going to be a simple "scale up fast, let it scale down slowly once our temporary need was over".)

Had the human-readable label in the UI said "E2 and N1 CPUs" instead of "CPUs" we would not have made that mistake: we would have tried for a smaller scale-up or requested more quota first.

I assume that the "internal"/computer-readable name `CPUS` is unlikely to change for compatibility reasons, but hopefully the UI display name is less hardcoded?

ak...@gmail.com <ak...@gmail.com> #4Mar 15, 2021 05:57AM

Very much needed. I could let my clients use 1Password to store their TOTPs (most of them use 1Password)

ak...@devrev.ai <ak...@devrev.ai> #5Apr 7, 2021 01:22PM

+1 It is contradictory for Google Identity Platform to provide a MFA option which Google itself considers insecure. It is one of the deciding factor for us picking a CIAM solution.

Issue 154359804