-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OOB Deprecation #6
Comments
Is it possible to do something like what jolla does for google accounts? |
It is, however the app or rather the OAuth api usage needs to be validated by google. Plus they added user caps. Here's an excerpt: The user cap limits the number of users that can grant permission to your app when requesting unapproved sensitive or restricted scopes. The user cap applies over the entire lifetime of the project, and it cannot be reset or changed. Verified apps will still display the user cap on this page, but the user cap does not apply if you are requesting only approved sensitive or restricted scopes. If your users are seeing the "unverified app" screen , it is because your OAuth request includes additional scopes that haven't been approved. I am going to give it one last attempt. Basically adhering to everything they state, starting with a project page and a privacy policy. |
I have resubmitted the app for verification. Project Page: cargo.roshan.jp |
That is one snazzy website! |
I got word back from Google.
Before resubmitting, I thought I should finally implement uploads and maybe a gallery patch to include Drive images(*.jpg, *.jpeg, *.png...ets.) Not sure about the gallery patch though. |
@attah mind testing out the new login method. Just remember to rename your old token. We're still not verified so you might get a warning from google. |
That worked like a charm! And just in time for when i need it (tomorrow) :) |
I'm not big on patches... but that looks pretty cool! |
Figured you'd say that. realized too late that we have PatchManager...smh. Will have removed. |
Since OOB has been deprecated, another method of authentication needs to take place. I suggest the following:
Users need to register their own apps through Google Console with the correct scope:
Trust me when I say this, you will never get verified. I spent like 45 minutes making a 10 second video to showcase why I need those scopes...yes they will ask you to upload a video through youtube...SMH. But that's not a problem. We can use InstalledAppFlow to hasten the process through a simple script and fetch the token without much refactoring: prototype example:
Note that this will not allow anyone other than the app creator access by default. If you were to authorize any other account you'll get the following
I dont think it prudent nor acceptable to state that this is what it is and user should proceed to authorize cargo to access their information.
The text was updated successfully, but these errors were encountered: