ferdium
Bug: login to slack organization
Avoid duplicates
- [X] I have searched the issues tracker for a bug report similar to mine, in vain
Ferdium Version
6.2.0
What Operating System are you using?
Other Linux
Operating System Version
Manjaro with kernel 5.15.76-1-MANJARO
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
I have a Slack account in an organization which should grant me access to two workspaces. I should access using Slack SSO. I should enter username and password for my email address. After that I should complete a check for 2-factor authentication and and get access to both workspaces
Actual Behavior
After I complete the 2-factor authentication check, Ferdium shows me a white screen, with a header with Ferdium - Slack - Forwaring ...
Steps to reproduce
- Have an account in a Slack organization with multiple workspaces
- Sign in with Slack SSO
- Enter username
- Enter password
- Complete 2-factor authentication step
- Be stuck on
Ferdium - Slack - Forwarding ...page
Debug link
https://debug.ferdium.org/29554707-0538-4135-834c-679025333061
Screenshots
No response
Additional information
Everything works correctly if I try the same procedure on a browser
I was able to login into slack using okta just yesterday for a new client.
One additional thing I noticed is that there is a call to https://{workspace}.slack.com/sso/saml which is in canceled status, while using a browser that call responds correctly with a 200
@guedressel it looks a bit different, since in my case I do see the screen for 2FA and I can complete that step. It's the next one which fails
I'm seeing the same issue - SAML login seems to work (including 2FA), but then it hits a blank page with the canceled request that @marcosh mentioned above. When going through the flow in a browser, after 2FA I'm taken to a page that allows me to select the workspace that I want to load (my 'Enterprise' has 3).
Confirm the issue, Slack with Google SSO, still occurring with the 6.2.6
I was able to get it working after changing the user agent under service settings.
I looked up the latest Edge user agent here : https://www.whatismybrowser.com/guides/the-latest-user-agent/edge
Switching user agent to edge on windows (even being on linux) fixed the issue. Even google SSO looked different.
I managed to login by changing the user agent, but now I'm stuck at the Workspace Directory. Choosing a workspace just opens it in a browser, while clicking Open in Ferdium redirects back to the Workspace Directory.
