In the native Slack, the following happens now:
As opposed to the native Slack client, the following happens in Franz:
Can share privately.
I presume it's only about Franz being able or allowing to show the standard HTTP Auth notification/input windows.
As above.
Logging in to Slack on our company instance.
5.0.0-beta.14.451
A solution could be to add a username and password field in the settings page. The link for the connection could then be updated (in case of HTTP AUTH login) to username:password@domain, or by using more native solutions for http auth in electron (like here, app::event-login)
@mroeling Maybe it's better to ask for the Basic HTTP Auth when it's requested, like in standard Slack UI for example, so the Franz itself don't need to have a mechanism to store the password securely, but the "inside" application itself :)
My assumption is that several people will be affected when the login goes through SSO instead of standard user/pass. Hopefully this makes the roadmap :)
+1 to this. I experience similar behavior, except in my case, Franz redirects to my SSO home page, and a new Chrome tab is opened with Slack web.
+1, currently cannot use Facebook Workplace or Slack with Franz because SSO uses HTTP auth
Seems like several business integrations, e.g. Facebook Workplace and Slack with SSO, cannot use Franz.
Rambox has the same issue, but it seems that they've given up on this.
+1 for this. Same issue with Microsoft Teams
Temporary workaround:
Franz > View > Toggle Service Developer Tools > Console
Replace USER and PASSWORD with your credentials and use this command:
window.location.href = window.location.protocol + "//" + "USER" + ":" + "PASSWORD" + "@" + window.location.hostname + (window.location.port ? ":" + window.location.port : "") + window.location.pathname + window.location.search
User and password values must be url-encoded: https://meyerweb.com/eric/tools/dencoder/
It appears this was fixed. I can now see our corporate SSO page and log in. Sometimes I need to reload the Slack instance in Franz but that's okay-ish.
@xanderiel still doesn't work for me on 1.8.4, what version are you using?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'd still benefit from being able to login using HTTP Digest auth. Will this request see the light of day?