Giters

ferdium / ferdium-app

All your services in one place, built by the community

Home Page:https://ferdium.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Microsoft Outlook and Teams "browser version isn't supported"

zworkinspace opened this issue · comments

commented

Avoid duplicates

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

Ferdium Version

6.7.3

What Operating System are you using?

macOS

Operating System Version

13.6.6

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

When adding a Teams (or Outlook) service and entering valid credentials the Teams page should load.

Actual Behavior

The Teams credentials (including 2FA) are successfully entered and appear to be accepted but an error message page is returned:
"Hmm. Your browser version isn't supported. ... "

Steps to reproduce

  1. Click on add service.
  2. Select Microsoft Teams.
  3. Enter User Agent: https://teams.microsoft.com
  4. Leave other settings to defaults.
  5. Save Service
  6. Enter credentials on Sign in panel for a valid Teams / O365 account

Debug link

No response

Screenshots

No response

Additional information

This may be entirely due to 0365 refusing to serve to other than supported Chromium browsers (Edge or Google Chrome), Safari or Firefox, and not something that can be fixed on the ferdium client side - ??

Might there be a way to have our 0365 cloud service provider configure the server to accept connections from ferdium's client?

Otherwise, THANKS for a great app that at least lets one integrate Slack, Mattermost and many other services to help reduce the desktop Tower of Babel problem.

commented

Note: rambox has exactly the same problem.

commented

Hello @zworkinspace, thank you for logging this issue.

Just to be clear, are you adding an URL to the user agent?

Enter User Agent: https://teams.microsoft.com

This is NOT how you change the user agent (and you shouldn't be doing it in the first place if the service works without it) - if that is the case, no wonder the service complains it doesn't know the browser you are in (you are saying you are using https://team.microsoft.com browser) 🙈

Let me know if you need further help to fix this!
If it is still an issue I think I might be able to find a workaround.

commented

well shoot, as I was going through the service setup it looked like I had to enter the URL similar to other services, it didn't occur to me to just create the service and open it!! Perhaps the documentation should make that clearer?

Upon deleting the Teams service that didn't work and creating a new one, leaving all parameters at default and simply opening it, I got to the login and was able to enter my account 2FA credentials.

Now I've got my assorted Slacks, Mattermosts and Teamses all in one place, slightly improving the chances I won't miss smoke signals on them.

Thanks, @SpecialAro , for your very prompt response and solution!