Re: [Evolution] Authentication Failures

[Milan Crha via evolution-list]

On Sun, 2022-10-23 at 16:25 -0500, Japhering, Anonymous via evolution-
list wrote:
> Any idea what verstion might have updates to address it ?

Hi,
it's this one:
https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/388
The 3.42.5 was the last version receiving the fix upstream.

I do not know why you use the old Flatpak version. Maybe you build it
yourself? Then I suggest you update the Flatpak manifest from the
branch you want to use, rather than stay so much behind:
https://gitlab.gnome.org/GNOME/evolution/-/blob/gnome-43/flatpak/org.gnome.Evolution-stable.json

You can also save your and yours' machine time by using the Flathub.org
version.

Bye,
Milan

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Evolution] Authentication Failures

[Japhering, Anonymous via evolution-list]

Evolution 3.40.4 (flatpak git04222ec) 
Linux Mint:  5.4.0-126-generic #142-Ubuntu
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=20.3
DISTRIB_CODENAME=una
DISTRIB_DESCRIPTION="Linux Mint 20.3 Una

Updated flatpak today and now I'm getting the following:


   Access blocked: Third-party app is using an unsupported OAuth method
   Google has safe ways for users to sign in and share their Google
   Account data with third-party applications. To help protect your
   account, Google sign-in requests are blocked from apps with less secure
   authorization methods because they’re more vulnerable to phishing and
   app impersonation attacks.
   
   Learn more about how your data is shared with third-party apps
   
   App sent an invalid request
   If the app is blocked because it uses an unsupported authorization
   method, you may be directed to an “Error 400” page that says “Access
   blocked: App sent an invalid request.”
   
   Info for app developers
   If your app uses the Loopback IP Address method for iOS, Android,
   and Chrome app OAuth client types or the Out-Of-Band method for any
   client type, you’ll need to migrate to a more secure alternative
   method. For detailed instructions, check the Out-Of-Band (OOO) flow
   migration guide and Loopback IP Address flow migration guide.
   
At the present time, my sessions are valid until they need to be
refreshed, at which point the above message appears. Currently, out of
the 8 accounts I use Evolution for .. 3 are throwing the aforementioned
error, the other 5 are still working.

Any idea what verstion might have updates to address it ?

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list