Closed Bug 1843537 Opened 2 years ago Closed 1 year ago

Slack and Element app authentication via auth0/SAML stuck on Nightly 117, works with release 115

Categories

(Fenix :: WebAuthn, defect, P1)

All
Android
defect

Tracking

(firefox116 wontfix, firefox117 fixed, firefox118+ fixed, firefox119 fixed)

RESOLVED FIXED
Tracking Status
firefox116 --- wontfix
firefox117 --- fixed
firefox118 + fixed
firefox119 --- fixed

People

(Reporter: jstutte, Assigned: royang)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Steps to reproduce

  1. New Android device, install Firefox Nightly and Release
  2. Make Nightly your default browser
  3. Install Slack (or Element)
  4. Connect to mozilla slack via auth0

Expected behavior

  • Default browser pops up and guides me through login
  • redirect to app, login done, can use slack

Actual behavior

Device information

  • Firefox version: 117.0a build 2015961955
  • Android device model: Samsung A54
  • Android OS version: 13

Any additional information?

If I set the current release version (115.2.0) as default browser, the flow works. Both browsers have no extensions and out-of-the-box preferences. I just connected them to my Firefox Account.

The severity field is not set for this bug.
:jmahon, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jmahon)
See Also: → 1845054

Hey Roger, is this related to what you're currently working on?

Flags: needinfo?(royang)
Severity: -- → S2
Priority: -- → P1

This could be a side affect of something we recently fixed in v117. I'll debug. Thanks

Flags: needinfo?(royang)
Assignee: nobody → royang
Keywords: regression
Regressed by: 1836971

Caused by https://bugzilla.mozilla.org/show_bug.cgi?id=1836971. Slack does not use custom tab when performing authentication. And since the user have "never" set to "open links in apps" we did not redirect back to slack app. This is a case where respecting user's choice broken the authentication flow. Reverting the change until a better solution can be found.

Set release status flags based on info from the regressing bug 1836971

Fixed in Nightly, please confirm. Thanks

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

This issue is still reproducible on the latest Nightly 118.0a1 from 17.08.2023. Users are unable to authenticate with Slack using Fenix.
Tested with Google Pixel 7 Pro (Android 14) and Motorola Moto G9 plus (Android 11).

(In reply to Adina Petridean from comment #7)

This issue is still reproducible on the latest Nightly 118.0a1 from 17.08.2023.
Tested with Google Pixel 7 Pro (Android 14) and Motorola Moto G9 plus (Android 11)

Did you check if it is instead still working with current release (116) ? That would point to some difference in default preferences between release and nightly.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

(In reply to Jens Stutte [:jstutte] from comment #8)

(In reply to Adina Petridean from comment #7)

This issue is still reproducible on the latest Nightly 118.0a1 from 17.08.2023.
Tested with Google Pixel 7 Pro (Android 14) and Motorola Moto G9 plus (Android 11)

Did you check if it is instead still working with current release (116) ? That would point to some difference in default preferences between release and nightly.

This issue is also reproducible on version 116.3.0 - build 2.

Ok, so something else landed probably during the 116 nightly cycle that makes this break, and it is not just bug 1836971? IIUC the initial change there has been reverted. I fear mozregression is not working for Android to help in bisecting?

(In reply to Jens Stutte [:jstutte] from comment #11)

Ok, so something else landed probably during the 116 nightly cycle that makes this break, and it is not just bug 1836971? IIUC the initial change there has been reverted. I fear mozregression is not working for Android to help in bisecting?

Mozregression is not working.

Jeff / Roger, can you touch base about this bug? Especially:

Most time-sensitive:

  • is it still happening?
  • is there a regression that's causing it? (if so, let's know what we need to back out in the next couple days before 118 goes out)

Less time-sensitive:

  • is it webauthn or deep linking?
Flags: needinfo?(royang)
Flags: needinfo?(jmahon)
Flags: needinfo?(jboek)

This issue is an "Open links in apps" issue. However, I'm unable to reproduce it with Nightly, or release(117.1.0) on any "Open links in apps" setting.
:apetridean, is this reproducible with v119? If so, what's your "Open links in apps" setting? And are you authenticating through Auth0? Thanks

Flags: needinfo?(royang) → needinfo?(apetridean)

is it webauthn or deep linking?

I just briefly looked at this, it's still on my list to investigate. But initially I don't believe that it is WebAuthn but an issue with deep linking. Will report back once I get the chance to dig into it.

I can no longer reproduce this issue with the latest nightly build (119.0a1 from 19.09.2023). The 'Open links in app' option is set to 'Never.'
I have verified this on Google Pixel 7 Pro (Android 14) and a Motorola Moto G9 Plus (Android 11).

Flags: needinfo?(apetridean)

Thanks for confirming. I'll mark this as fixed.

Status: REOPENED → RESOLVED
Closed: 2 years ago1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: