Ferdi: Slack - cannot authenticate / access

[wernerdiers]

" are comments from us and won't be
visible in your bug report, so please don't put any text in them.
-->
Bug description:
Slack in my organization is tied to Okta and Google authentication.
From a clean install, i add Slack service to my workspace. I enter my credentials, then i get the Okta console and then it is stuck in the Sing in screen.

Other services that uses Okta or Google auth are working (e.g. Gmail, Trello, Evernote, etc)

Steps to reproduce:

1. Slack tied to Okta and Google authentication.
2. From a clean install, add Slack service to your workspace.
3. Enter credentials
4. Then it is stuck in the Sing in screen instead of login to the Slack group

Expected behavior
Be able to access Slack group and channels after authentication

Screenshots

Environment:

• Operating System: macOS Mojave
• Ferdi Version: 5.5.0.2116

• Server: Ferdi with account

• Debug information:
  Attached

devconsole.log

debugingo.log

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.61. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[raicerk]

Hi, I have the same problem, my slack use saml authentication, when I enter the data to login, the callback of slack return the login of slack and don't having access

[wernerdiers]

Hi team, just checking if there is an update.

[wernerdiers]

@raicerk were you able to workaround this issue?

[gleonet]

Same problem here. Slack + Google authentication doesn't work with Ferdi

Ferdi Version: 5.5.0.2116
OS : Ubuntu 20.04

[raicerk]

@wernerdiers no, I have not been able to solve it, so I analyzed, the problem is in the forwarding of the authentication keys that google has

[Malwurf]

Same issue on Ubuntu 20.04.1 LTS | Ferdi version 5.5.0 -> after logout from slack can't log in with 'Sign in with Google'

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. Please check if this issue is still relevant and please close it if it's not. This will make sure that our open issues are actually of use and reduce the list of obsolete issues. Thank you for your contributions.

[YNedderhoff]

I have the same problem on MacOS 10.14.5