Google Sign In

Status
Not open for further replies.

gjassal

Free User
Joined
Apr 2, 2019
Messages
30
Reaction score
2
Trying to have backups store to google drive but getting an error when trying to login with my google account.
Just did this the other day and it was working fine.

"This app has not been verified yet by Google in order to use Google Sign In."
 
Google, rightly, improves the security of APPs. However, in the way we would need it, we would need to declare all redirect URLs and as you can imagine this is impossible to do. You may still use it with the warning for now. As a replacement, we will extend our destination locations to:
U4 --> sFTP, SMB and FTPs
U5 --> Google Storage (Bucket), Azure Storage, Amazone S3
(given that we manage to do them all)
 
  • Like
Reactions: Evolute IT
Google, rightly, improves the security of APPs. However, in the way we would need it, we would need to declare all redirect URLs and as you can imagine this is impossible to do. You may still use it with the warning for now.

After reading the FAQ on the new requirements, they seem to specifically address the issues:

"4) If drive.file is not a possible option (e.g. for backup clients), you should begin preparing your app for the restricted scope verification, a process that, among other steps, ensures your use of data is compliant with the Limited Use Requirements and includes a security assessment if your app stores or transmits through servers. Restricted scope verification for the Drive API will begin early next year. Refer to the FAQ for more info."

It looks like they will allow you to get 3CX verified as a "Restricted Scope" app. If it isn't on the roadmap, let me be the 1st to request it. :-) Literally all my clients at the moment use Google drive to backup their 3CX installs. It's free, works well, and is expandable at a reasonable price. Thanks for the quick response!
 
Google, rightly, improves the security of APPs. However, in the way we would need it, we would need to declare all redirect URLs and as you can imagine this is impossible to do. You may still use it with the warning for now. As a replacement, we will extend our destination locations to:
U4 --> sFTP, SMB and FTPs
U5 --> Google Storage (Bucket), Azure Storage, Amazone S3
(given that we manage to do them all)

Is there a workaround for this until the new storage solutions are in place?
 
After reading the FAQ on the new requirements, they seem to specifically address the issues:

Rest assured, we submitted it. However, the max target domains are limited and custom domains will not work period. Hence the feature will be replaced with options which are available for all of our customers. U4 will provide a transfer tool to move to another store location.
 
  • Like
Reactions: Evolute IT
Status
Not open for further replies.

Forum statistics

Threads
111,934
Messages
589,819
Members
164,811
Latest member
aurorasigntrtechitnet