Assigned
Status Update
Comments
ba...@google.com <ba...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
kd...@gmail.com <kd...@gmail.com> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
kd...@gmail.com <kd...@gmail.com> #4
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
kd...@gmail.com <kd...@gmail.com> #5
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com>
sy...@gmail.com <sy...@gmail.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
Description
Recently, our web application that uses OAuth2.0 authentication to connect to Google Drive has encountered a problem.
We already registered and verified our application (through Google Console),and has not encountered this error before until March 9, 2022.
The following error is displayed after the username has been inputted:
PROBLEM: "This browser or app may not secure"
Upon redirecting the user to Google OAuth screen, the user will be able to input their username.
However, when the user tries to proceed to password screen, they are prompted with the error (image attached).
On March 8, 2022 and previous dates, we were able to use the app without this error.
However on March 9, 2022, the error suddenly appeared.
We also already checked the following Sign in with a supported browser - Computer - Google Account Help and made sure that:
1. JavaScript is turned on
2. This is not a security or network issue in our work network since we can access just fine using other browsers (Chrome, Edge).
3. We are using browser-based OAuth2.0
Our initial thought is that Google may have updated their policy or OAuth2.0 contents, but we have not seen any announcement about it.
The application version we have used on the day the error occurred and the prior dates are the same.
This is the browser where the error occurs:
Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/534.34 (KHTML, like Gecko) qtbrowser/0.1
Is this browser not supported by Google anymore?