Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Jeremy Bícha]

On Tue, Feb 20, 2024 at 8:18 PM Alban Browaeys  wrote:
> gnome-control-center 46~beta-1 is supposed to already be ported to the
> new gnome-online-accounts gtk4 API, from
> " online-accounts: port to new API"
> https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/80fcc8c2f26f7561538418fc5d72e18ecbbe512b
> so I believe that in sid gnome-control-center 46~beta-1, managing
> accounts from gnome-online-accounts should already broken.
> But installing this sid version, I can still show all accounts details
> with gnome-online-accounts 3.49.0. I can also remove and adda kerberos
> account.

The new gnome-online-accounts API was implemented in
gnome-control-center upstream version 46.beta.1. In Debian, we adjust
the first . to ~ to make 46~beta.1 (to ensure that 46~beta sorts lower
than 46.0). The downstream Debian version is the part of the version
number after the final - . So, 46~beta-1 is actually upstream's
46.beta instead of 46.beta.1. The final -1 just means this is the
"first" Debian revision for that upstream version. Sorry, that it is
so confusing here.

Yes, we intentionally did not package 46.beta.2 (or beta.1) yet
because of how disruptive the new gnome-online-accounts version will
be. It will take some time to think about how to handle it.

Thank you,
Jeremy Bícha

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Alban Browaeys]

On Wed, 21 Feb 2024 01:43:11 +0100 Alban Browaeys 
wrote:
> Note that 3.49.1 also includes a migration to GTK4 and API changes
> which would breaks gnome-control-center 45 "Bump soname?"
> https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/291
> Though we have gnome-control-center 46~alpha-2 in trixie and 46~beta-
1
> in sid, I don't know which gnome-control-center 46 release was ported
> to this API (as I have 1:46~alpha-2 currently I believe it is not
> ported yet as it works with gnome-online-accounts 3.49.0).
> 


gnome-control-center 46~beta-1 is supposed to already be ported to the
new gnome-online-accounts gtk4 API, from
" online-accounts: port to new API"
https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/80fcc8c2f26f7561538418fc5d72e18ecbbe512b
so I believe that in sid gnome-control-center 46~beta-1, managing
accounts from gnome-online-accounts should already broken.
But installing this sid version, I can still show all accounts details
with gnome-online-accounts 3.49.0. I can also remove and adda kerberos
account.

Cheers,
Alban

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Alban Browaeys]

The 405 status was locally and manually fixed by applying the "webdav
migration" implemented upstream in merge request 146.

That is in ~/.config/goa-1.0/accounts.conf for my owncloud provider,
add "remote.php/webdav" to the "https://nextcloud.domain/; in the "Uri"
key.
I also create CalDavUri and CardDavUri from the "Uri" key but appending
"remote.php/dav" to them instead of "remote.php/webdav".
I got the clue from the issue "critical when testing new WebDav support
on existing nextcloud account: g_uri_peek_scheme: assertion 'uri !=
NULL' failed"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/276 ).


The fix: "goabackend: migrate existing WebDAV
accounts"https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/146
It is merged in 3.49.1 (while Debian is 3.49.0).

Note that 3.49.1 also includes a migration to GTK4 and API changes
which would breaks gnome-control-center 45 "Bump soname?"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/291
Though we have gnome-control-center 46~alpha-2 in trixie and 46~beta-1
in sid, I don't know which gnome-control-center 46 release was ported
to this API (as I have 1:46~alpha-2 currently I believe it is not
ported yet as it works with gnome-online-accounts 3.49.0).

Might be the best way for now is to port the merge request 146 to
3.49.0 in Debian trixie.

The API breakage in gnome-control-center was done in "goabackend: port
to GTK4"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/142
which is merged into 3.49.1.

Cheers,
Alban

On Sat, 27 Jan 2024 08:11:10 +0100 Alban Browaeys 
wrote:
> Package: gnome-online-accounts
> Version: 3.49.0-1
> Severity: important
> 
> 
> I upgrade gnome-online-accounts from 3.48.0-2 to 3.49.0-1, I still
had
> Nextcloud ok in gnome-control-center (Settings) 1:46~alpha-2.
> Then on one box I rebooted, then I got "Credential have expired" for
> Nextcloud in Settings. Trying to authenticate anew gave me "Error
> connecting to WebDAV server: Authentication failed".
> 
> I then tried on the other box, which still had nextcloud login ok,
where
> I also upgraded gnome-control-center but did not yet restart it, to
> kill goa-daemon and restart it. Then I ended up with the same error
as
> wiht the box I rebooted.
> 
> Settings output is:
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting new address enumeration
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: lookup_by_name_with_flags_async: starting new lookup for
cloud.prahal.homelinux.net with GTask 0x5581b3e13eb0, LookupData
0x5581b3ce9500
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: lookup_by_name_with_flags_async: starting new lookup for
cloud.prahal.homelinux.net with GTask 0x5581b3d76160, LookupData
0x5581b3d1c5b0
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Address enumeration succeeded
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting TCP connection attempt
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: TCP connection successful
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting application layer connection
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Connection successful!
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]:
GoaBackend: goa_dav_client_check(): response (0x5581b422b970, 405)
> 
> Note the 405 status.
> Could it be my old Nextcloud version does not support a method call
from
> goa 0.49.0?
> 

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Richard B. Kreckel]

On 2/5/24 00:08, Jeremy Bícha wrote:

I do not believe your issue is the same since you are still able to
log in to your NextCloud, but the original bug poster is not.


Okay.


Yes, I believe it is expected that updating GNOME Online Accounts to
3.49 will require reauthenticating. Authentication is now handled in
the user's regular web browser instead of a webkitgtk dialog which
makes login more reliable and should be more resilient to
authentication changes from upstream providers.


I was looking for information like this pointing out the 
incompatibility. (The changelog does mention that authentication for 
Google & Microsoft now uses the web browser, but nothing about nextCloud 
etc.)



It is not expected that everything will work if you try to share
configuration between different operating system versions. Sorry.


:(   Ouch! This is so frustrating.

  -richy.
--
Richard B. Kreckel

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Jeremy Bícha]

On Sun, Feb 4, 2024 at 4:42 PM Richard B. Kreckel  wrote:
> Confirmed: Same problem here for nextCloud and for google accounts.

I do not believe your issue is the same since you are still able to
log in to your NextCloud, but the original bug poster is not.

> I can remove the accounts and re-add them. But then they don't work with
> gnome-online-accounts 3.46.0-1 (Debian stable machine where same home
> dir is mounted). There, I can remove them and re-add them. But changing
> to 3.49.0-1 from testing all starts over again.

Yes, I believe it is expected that updating GNOME Online Accounts to
3.49 will require reauthenticating. Authentication is now handled in
the user's regular web browser instead of a webkitgtk dialog which
makes login more reliable and should be more resilient to
authentication changes from upstream providers.

It is not expected that everything will work if you try to share
configuration between different operating system versions. Sorry.

Thank you,
Jeremy Bícha

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Richard B. Kreckel]

Confirmed: Same problem here for nextCloud and for google accounts.

Gnome files says "Unable to access usern...@googlemail.com Invalid 
credentials for usern...@googlemail.com".
Same for nextCloud accounts. goa-daemon says 
"/org/gnome/OnlineAccounts/Accounts/account_1706819076_1: Setting 
AttentionNeeded to TRUE
 because EnsureCredentials() failed with: Invalid password with 
username “username” (goa-error-quark, 4): Authentication failed (goa-e

rror-quark, 4)

I can remove the accounts and re-add them. But then they don't work with 
gnome-online-accounts 3.46.0-1 (Debian stable machine where same home 
dir is mounted). There, I can remove them and re-add them. But changing 
to 3.49.0-1 from testing all starts over again.


Seems like compatibility broke badly.

Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Alban Browaeys]

Package: gnome-online-accounts
Version: 3.49.0-1
Severity: important


I upgrade gnome-online-accounts from 3.48.0-2 to 3.49.0-1, I still had
Nextcloud ok in gnome-control-center (Settings) 1:46~alpha-2.
Then on one box I rebooted, then I got "Credential have expired" for
Nextcloud in Settings. Trying to authenticate anew gave me "Error
connecting to WebDAV server: Authentication failed".

I then tried on the other box, which still had nextcloud login ok, where
I also upgraded gnome-control-center but did not yet restart it, to
kill goa-daemon and restart it. Then I ended up with the same error as
wiht the box I rebooted.

Settings output is:
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting new address enumeration
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x5581b3e13eb0, LookupData 0x5581b3ce9500
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x5581b3d76160, LookupData 0x5581b3d1c5b0
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Address enumeration succeeded
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting TCP connection attempt
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: TCP connection successful
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Starting application layer connection
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-GIO: 
GSocketClient: Connection successful!
janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GoaBackend: 
goa_dav_client_check(): response (0x5581b422b970, 405)

Note the 405 status.
Could it be my old Nextcloud version does not support a method call from
goa 0.49.0?

PS: I will probably open a bug report against upstream has I believe
this issue not to be Debian related. Though I wanted to raise your
awareness of the issue (which might not affect all Nextcloud instances),
even though this gnome-online-account update already hit testing.

Best Regards,
Alban

I also see that in G_MESSAGES_DEBUG=all /usr/libexec/goa-daemon
--replace output:

(goa-daemon:128630): goa-daemon-DEBUG: 08:00:12.384: 83448041499: Received 
EnsureCredentials (owncloud, account_1674792379_0)
(goa-daemon:128630): goa-daemon-DEBUG: 08:00:12.384: 83448041568: Handling 
EnsureCredentials (owncloud, account_1674792379_0)
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.386: Retrieved keyring 
credentials for id: account_1674792379_0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: GSocketClient: Starting new 
address enumeration
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x7f6324c4d6f0, LookupData 0x7f6324c4d6a0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.386: 
lookup_by_name_with_flags_async: starting new lookup for 
cloud.prahal.homelinux.net with GTask 0x7f6324c63320, LookupData 0x7f6324c632d0
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Address 
enumeration succeeded
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Starting TCP 
connection attempt
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: TCP 
connection successful
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Starting 
application layer connection
(goa-daemon:128630): GLib-GIO-DEBUG: 08:00:12.388: GSocketClient: Connection 
successful!
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S0] [-] 
[SEND] [SETTINGS] stream_id=0
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S0] [-] 
[SEND] [WINDOW_UPDATE] stream_id=0
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] [NONE] 
[SESSION] Request made for cloud.prahal.homelinux.net/
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] [NONE] 
[SESSION] State NONE -> WRITE_HEADERS
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] 
[WRITE_HEADERS] [SEND] [HEADERS] stream_id=1, category=REQUEST finished=1
(goa-daemon:128630): libsoup-http2-DEBUG: 08:00:12.423: [CLIENT] [C1-S1] 
[WRITE_HEADERS] [SESSION] State WRITE_HEADERS -> WRITE_DONE
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > OPTIONS / HTTP/2
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Soup-Debug-Timestamp: 
1706338812
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Soup-Debug: SoupSession 
1 (0x7f63249e4930), SoupMessage 1 (0x7f63246cd830), GSocket 1 (0x7f6324b3f300)
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > Accept-Encoding: gzip, 
deflate, br
(goa-daemon:128630): GoaBackend-DEBUG: 08:00:12.423: > User-Agent: 
gnome-online-accounts/3.49.0