| Index > Scribe > Is there full support for OAuth? | |
|---|---|
| Author/Date | Is there full support for OAuth? |
| lwc 17/04/2021 7:54pm | Servers like Gmail (especially the commercial version) can no longer work without OAuth, is there support for it?
In Account=>Configure, there is OAUTH2 under Authentication Type, but I'm not sure it's done right as you also ask for username/password, and the whole point in OAuth is not to ask them yourself. OAuth is supposed to launch a browser window from, for example Gmail, and register Scribe in the online account. I've installed SSL, but no matter which settings I've tried in Scribe no connection occurred and worse still not a single error message popped up to explain what's going on. Eventually, I've noticed the bottom window (Account) states errors such: Error: OpenSSLSocket.cpp:886 - 10008:error:2008F002:BIO routines:BIO_lookup_ex:system lib:crypto\bio\b_addr.c:730:N SSL connection closed. ScribeImap_Thread.cpp:802 - IMAP connection to imap.google.com:993 failed.   |
| lwc 20/04/2021 8:18am | Well, the whole issue was I wrote imap.google instead of imap.gmail...
Once I wrote it correctly, it popped up the browser to approve OAuth. However, why did it write: Google hasn’t verified this app The app is requesting access to sensitive info in your Google Account. Until the developer verifies this app with Google, you shouldn't use it. ? Will you consider verifying it? I guess it's done through https://support.google.com/cloud/answer/9110914  |
| fret 20/04/2021 9:05am | Yeah I know about that. I did try and get it verified, and they initially responded querying the scopes I was using. I adjusted those and resubmitted it some time later. They then stopped responding to me and I don't know how to restart the process again. I can't cancel the existing verification and can't move forward either. Google FTW hey. |
| luke 28/07/2024 4:53am | A lot of product including Zoom desktop seems to be able to access gmail with their latest requirement, aka, "sign in with Google".
For geeks with open source email client, they can start with creating their own gmail API app like they do with claws-mail: https://www.claws-mail.org/faq/index.php/Oauth2 Basically one needs to: 1. sign into google and sign up as a developer 2. create a project with whatever name they want 3. fill out the OAuth settings with their email (scopes are requested by the application, skip it) 4. create the OAuth client and save the Credentials for the application to use 5. With the OAuth credentials, request the authorization token with web browser and get it at the url callback (need to use an unoccupied port and ensure windows firewall doesn't block it). Bingo! Similarly with other providers like Microsoft and Yahoo. |
| Reply | |