Oauth login failure via ChromeOS Playstore app

[leeIco3]

Description:

When trying to login to to self hosted or open workspace clicking the oauth google login generates the codes and opens in chrome and the request is returned to the app but the app then does nothing with the response, therefore failing to login.

Only seems to happen under Chrome OS using the mobile client via the playstore, have tried beta client and experimental with no success.

Environment Information:

• Rocket.Chat Server Version:
• Rocket.Chat App Version:4.19.0.25555
• Device Name:
• OS Version: ChromeOS 93.0.4577.69

Steps to reproduce:

1. Click join a workspace
2. enter workspace to join or open workspace
3. click login
4. click continue with google
5. browser opens and returns to app
6. app remains unchanged with "continue with google" option

Expected behavior:

Expect for callback to be handled/received and generate login and proceed.

Actual behavior:

App remains in unauthed state and leaves the button with continue with google inplace (still active and clickable)

Additional context:

I assume the way the oauth is implemented needs to change to handle how chromeos is doing playstore apps now ? Ive tried on multiple chromeOS machines so its not specific to me and even the open workspace setup doesnt work with google login which removes the issue in our selfhosted version.

[miko007]

we experience a similar (if not the same) issue in the latest iOS build.

[MaxWaldorf]

I confirm the same issue on android and IOS with custom OAuth...

https://forums.rocket.chat/t/rocket-chat-4-0-android-mobile-app-4-20-0-26005/12329

[LevyCosta]

Hey @leeIco3. Thanks for reporting this. With yours and @MaxWaldorf's comments, we were able to reproduce it and we are working on isolating the issue.

[tcdev0]

same here :(

Versions:
server: 4.0.1
app: 4.20.0.26006

[MightyGoldenOctopus]

Same with our installation since we updated from 3.18 to 4.0.1, all mobile users both on Android and iOS experience the same issue, mobile app is now completely unusable for our users.

[reinaldonetof]

Same with our installation since we updated from 3.18 to 4.0.1, all mobile users both on Android and iOS experience the same issue, mobile app is now completely unusable for our users.

Hi @MightyGoldenOctopus, could you share with us which oAuth you are trying to access?

[MightyGoldenOctopus]

Same with our installation since we updated from 3.18 to 4.0.1, all mobile users both on Android and iOS experience the same issue, mobile app is now completely unusable for our users.

Hi @MightyGoldenOctopus, could you share with us which oAuth you are trying to access?

Hey @reinaldonetof, we are trying to access to our Microsoft Azure Active Directory oAuth.

[reinaldonetof]

Hey @reinaldonetof, we are trying to access to our Microsoft Azure Active Directory oAuth.

Interesting, so it's a custom oAuth, right? Is it working properly on the web?

[MightyGoldenOctopus]

Hey @reinaldonetof, we are trying to access to our Microsoft Azure Active Directory oAuth.

Interesting, so it's a custom oAuth, right? Is it working properly on the web?

Yes it is a custom oAuth. We do not experience any issue with the oAuth on the web browser.

[reinaldonetof]

Nice, so it is an enterprise server! Thank you all!

Then, we will add both custom and normal oAuth to our sprint.

We are running a "normal" (docker, no license or sth) Rocket.Chat instance with auth via custom OAuth2 from Mailcow. We are experiencing the same issue with the latest android app as well as with the latest iOS app. Because of this issue we are having heavy problems in team communication of our community project.

[diegolmello]

We've been working on a fix on the server side. Thanks!

[birgit-egroupware]

Any ideas when the big is fixed?

[MightyGoldenOctopus]

@birgit-egroupware It's the PR #23541 in the server repository which is planned to be distributed by the release 4.0.5