I follow the link in the message alpine shows when I try to go to
the folder, and get in the browser what I reproduce bellow.
Any hint?
Thanks in advance
Rodrigo
--
Authorization Error
Error 403: access_denied
The developer hasn�t given you access to this app. It�s currently being tested and it hasn�t been verified by Google. If you think you should have access, contact the developer ([email protected]).
Learn more
Dear Rodrigo, go back to the page you accessed to create your client-id and client-secret and make sure you "publish" your app. Go back an check in the "OAuth consent screen" that your app is "in production" and not in testing.
Dear Rodrigo, go back to the page you accessed to create your client-id and client-secret and make sure you "publish" your app. Go back an check in the "OAuth consent screen" that your app is "in production" and not in testing.
On Fri, 4 Mar 2022, Eduardo Chappa wrote:
Dear Rodrigo, go back to the page you accessed to create your client-id
and client-secret and make sure you "publish" your app. Go back an
check in the "OAuth consent screen" that your app is "in production"
and not in testing.
Well I did only one thing: go to "oauth consent" and click on "publish",
then it was not more "test", but "in production".
Was something else necessary?
On Fri, 4 Mar 2022, Roderick wrote:
Well I did only one thing: go to "oauth consent" and click on "publish",
then it was not more "test", but "in production".
Was something else necessary?
I do not think so. Are you having any other problems?
On Fri, 4 Mar 2022, Eduardo Chappa wrote:
Dear Rodrigo, go back to the page you accessed to create your client-id and >> client-secret and make sure you "publish" your app. Go back an check in the >> "OAuth consent screen" that your app is "in production" and not in testing.
Dear Eduardo,
thanks. Now I get what it is written below.
Rodrigo
---
Authorization Error
Error 400: invalid_request
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure.
You can let the app developer know that this app doesn't comply with one or more Google validation rules.
Request Details
The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.
If you�re the app developer, make sure that these request details comply with
Google policies.
redirect_uri: urn:ietf:wg:oauth:2.0:oob
I deleted all coockes. Now I get the same message, but in german.
Google does not ask for login before.
Rodrigo
Authorization Error
Error 400: invalid_request
You can't sign in to this app because it doesn't comply with Google's
OAuth 2.0 policy for keeping apps secure.
You can let the app developer know that this app doesn't comply with
one or more Google validation rules.
Let me tell you the steps you should make to configure Alpine.
* Go to gmail to get your client-id and client-secret. Publish your app.
* In alpine go to the main screen and press "S U". Replace the values
for client-id and client-secret that exist in Alpine with the ones you
got from Google. Make sure you add your gmail address under username.
* Now attempt to open the folder and just follow the link that Alpine
will give you. Make sure the client-id you are using is the one you
got from Google.
According to Eduardo Chappa <[email protected]>:
Let me tell you the steps you should make to configure Alpine.
* Go to gmail to get your client-id and client-secret. Publish your app. >> * In alpine go to the main screen and press "S U". Replace the values
for client-id and client-secret that exist in Alpine with the ones you >> got from Google. Make sure you add your gmail address under username.
* Now attempt to open the folder and just follow the link that Alpine
will give you. Make sure the client-id you are using is the one you
got from Google.
Running Alpine on the Mac, compiled from recent github source, I get the
same thing, Error 400: invalid request.
On Sat, 5 Mar 2022, John Levine wrote:
Running Alpine on the Mac, compiled from recent github source, I get
the same thing, Error 400: invalid request.
I do not use github, so please try this with the repository at
https://repo.or.cz/alpine.git
On Sat, 5 Mar 2022, Eduardo Chappa wrote:
On Sat, 5 Mar 2022, John Levine wrote:
Running Alpine on the Mac, compiled from recent github source, I get
the same thing, Error 400: invalid request.
I do not use github, so please try this with the repository at
https://repo.or.cz/alpine.git
there are a number of things happening that I am not sure you are telling
me about, but I think we need to make sure you and I are at the same place.
Let me tell you the steps you should make to configure Alpine.
* Go to gmail to get your client-id and client-secret. Publish your app.
* In alpine go to the main screen and press "S U". Replace the values
for client-id and client-secret that exist in Alpine with the ones you
got from Google. Make sure you add your gmail address under username.
* Now attempt to open the folder and just follow the link that Alpine
will give you. Make sure the client-id you are using is the one you
got from Google.
Sorry, I meant that it was a clone of your repo.
I do
$ ./configure --enable-from-encoding
and then build.
Dear Eduardo,
it is this third step that fails. I recognize the correct ID in the link alpine gives me.
I googled a little and found this:
https://laravelshowcase.com/question/google-oauth-from-localhost-throws-invalid_request-error
It seems that a solution has been found to this issue, but needs to be tested by more people, but here is something that seems to be working for some people.
On Sun, 6 Mar 2022, Eduardo Chappa wrote:
It seems that a solution has been found to this issue, but needs to be
tested by more people, but here is something that seems to be working
for some people.
For 7 days.
Google anounced, end of may they will only allow "secure apps". It
seems, we will have to do our Email work with android smartphones. I
regret that I decided to use gmail as my main email account, I never
though this was a trap.
The question is why google rejects alpine as not fulfilling who
knows what. And even if the problem is solved, it seems google
changes the rules continuosly, one cannot rely on google.
The question is why google rejects alpine as not fulfilling who knows
what. And even if the problem is solved, it seems google changes the
rules continuosly, one cannot rely on google.
IMO, Google has legitimate security concerns about any app trying to
access its services. For the record, I am certain, after using
Pine/Alpine literally decades, Google has no legitimate beef with
Eduardo et al about Pine/Alpine security.
The actual subsurface issue all advertising based business models like
Google have with CLI apps (like Alpine) is simple: money.
You can't as easily track and bombard consumers with ads on a CLI app, because it's ... CLI. Graphics and glitz are not strong suit draws for
CLI; access and speed on low-resorce gear, are draws.
It's why I still use lynx (or links) for some browsing. Who needs
obnoxious distracting advertisement overloading?
What's amazing to me is that Google actually even cares the least
bit about Alpine (etc) support.
client-secret that you are using with Alpine. You do not need to get a client-id and client-secret anymore, all you need to do is to authorize Alpine every week using the same client-id and client-secret.
And again, in test modus ouath2.py works.
lies perhaps the problem in the configuration of the project in the
google portal?
This authorization process is not simple, and with my nettop, when I am
not at home, difficult, if not impossible.
The question is why google rejects alpine as not fulfilling who knows
what. And even if the problem is solved, it seems google changes the
rules continuosly, one cannot rely on google.
When I have time, I will try alpine with mbsync and msmtp, for working offline, by far not a solution, but an alternative when things do not
work. See:
http://blog.onodera.asia/2020/06/how-to-use-google-g-suite-oauth2-with.html
Or is there other alternative?
On Sun, 20 Mar 2022, Eduardo Chappa wrote:
client-secret that you are using with Alpine. You do not need to get a
client-id and client-secret anymore, all you need to do is to authorize
Alpine every week using the same client-id and client-secret.
May I ask how?
I get the message: token has ben expired or revoked. No offer to
enter a new token, no instructions how to get it.
How to get the new token and how to enter it in alpine?
Thanks
Rodrigo
I got the screen with the authorization info (links to google, C command
to enter code). It seems a ^C spoiled the password file, because I had
to enter passwords again, this deleted perhaps also the invalid tokens,
what made the screen to appear.
Is the solution to delete the password file (with the tokens) in order
to get the screen with the links?
Recreating the password file willsend you to that screen, but you should be sent to that screen even if you do not remove the password file. If you are not being sent to that screen, can you run alpine with the command
alpine -d http
and look into there to see if you can identify the issue in the debug file?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 154:07:28 |
| Calls: | 12,091 |
| Calls today: | 4 |
| Files: | 15,000 |
| Messages: | 6,517,674 |