ferdium-app icon indicating copy to clipboard operation
ferdium-app copied to clipboard

Login Issue with Slack + Gmail + Google Calendar

Open kpinegar2 opened this issue 9 months ago • 4 comments

Avoid duplicates

  • [x] I agree to follow the Code of Conduct that this project adheres to.
  • [x] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

7.0.0

What Operating System are you using?

macOS

Operating System Version

Sequoia Version 15.3.1 (24D70)

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Ferdium version

7.0.0

Expected Behavior

Being able to log into gMail, google calendar, slack.

Actual Behavior

I'm having an impossible time logging into any of these services that I've been using forever on Ferdium. I have been out of the office and away from my computer for a couple weeks, which logged me out unlike usual, but I have no way to get back in as the app isn't working for me at all.

For Slack, I can log in, but the issue is that (even though I have the setting "Open URLs within Ferdium" checked, it keeps opening it in my browser every time). Even if I right click the correct workspace and click "Open in Ferdium", it just refreshes and goes nowhere.

For gMail + Google Calendar, it just won't log me in. I can load into our SSO login page, login with my credentials, and then the page just goes white every single time. I've tried being patient, but even after an hour it's still white and clearly not working.

This has happened to me before after an extended period away from my computer, but unlike then I cannot figure out how to fix it. I love Ferdium(!), but it's 100% unusable for me at this point in time (I suspect this issue is only for users like me who are logging in through SSO as I AM able to log in to my personal gMail account which doesn't require SSO).

Steps to reproduce

I'm not sure exactly how you could reproduce 100% without my login credentials for our company's SSO. I would be happy to get on a screenshare (in addition to the screenshots here) if that was helpful though! Tbh, I'm guessing it would either be a quick fix for y'all, or nothing you can do...

Debug link

No response

Screenshots

Image Image

Additional information

No response

kpinegar2 avatar Mar 14 '25 17:03 kpinegar2

I am having this exact same issue

jin-ahn avatar Mar 20 '25 22:03 jin-ahn

I had the same issue - until I updated the "Team" setting in the service settings. According to your screenshot, you should use the "redhat-internal" team-name

ableischwitz avatar Mar 24 '25 08:03 ableischwitz

same here.

Using Google-Services with a company SSO ends in a blank page. In a browser (firefox, chromium), it works as intended. Google does not report any errors with the login. When adding a Service, I get the first google-login page asking for the email. Then I get (correctly) redirected to our SSO and login. Then I get a redirect to a google-page, for a short while some google loading spinner is shown, then a blank page. The blank page has a URL like this https://accounts.google.com/a/COMPANY_DOMAIN/acs. So, If my SSO-enabled company were example.com, it would be https://accounts.google.com/a/example.com/acs

The same goes for Google Meet.

How can I help resolve this? What do you need?

EDIT:

Ferdium Version

7.0.0

flatpak says:

          ID: org.ferdium.Ferdium
         Ref: app/org.ferdium.Ferdium/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 7.0.0
     License: Apache-2.0
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 481,1 MB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: d4254e5dd46264b20802c8024641415c410f6154a41c84022747baccc0c629dc
      Parent: a18f9c0e0d22e56485701e6eb5ebcf695ecc2a23c9cab2d26db7f367ef818ed2
     Subject: Update ferdium-desktop module (a303ffd0)
        Date: 2024-11-11 19:42:31 +0000

What Operating System are you using?

Pop!_OS

Operating System Version

22.04 LTS, Gnome 42.9, X11

What arch are you using?

x86_64

Last Known Working Ferdium version

Somewhen before 2024-11-25, so most likely 6.7.*

I do not remember when I updated Ferdium, but I was using it before and it was working. Therefore I conclude that it broke between 6.7.* and 7.0.

kronn avatar Apr 03 '25 07:04 kronn

Duplicate of #1973 ?

k-y avatar May 02 '25 18:05 k-y