I started with a new company and they use a Federated AD via OS33 for authentication. The OS33 authentication requires the use of their mobile authentication app. Basically, when you log in via a browser or (windows) workstation the OS33 app pops up on the users mobile and does the “Is this really you? YES/NO”.
it looks like the WebKitGTK cannot handle the OAuth2 wizard (or the
site rejects this user agent), thus it stays empty (it’s that
blank/white rectangle below the URL on your screenshot). There are
several other folks claiming similar issue from time to time. I do not
recall whether it has any real fix, other than opening the URL in
another browser, follow the OAuth2 wizard and copy the authentication
code back to the Evolution. The tricky part is that this had been added
only in 3.46.x series, very recently. You can read the following thread
for an information how to get the latest Evolution series into older
for a price of some limitations (read the whole thread, please).
in the updated Evolution, you’ll see a little arrow beside the URL, on
the right side. When you click on it it’ll open your default browser
with that URL and the UI will change in the window, instead of looking
on the empty page there will be an entry for the authorization code,
with some explanation text.
Installing the latest version of Evolution, 3.46.3 (by Flathub.org), via flatpak worked. Thank you. The flatpak version allows me to connect and authenticate using the little “arrow” next to the URL and entering the code from the returned URL (code=XXXXX).