All users were logged out of Bugzilla on October 13th, 2018

400 Bad Request error when trying to log into Air Mozilla using Auth0 on my Samsung TV browser

VERIFIED FIXED

Status

VERIFIED FIXED
2 years ago
2 years ago

People

(Reporter: cpeterson, Assigned: kang)

Tracking

Details

(URL)

(Reporter)

Description

2 years ago
I am unable to log into Air Mozilla using Auth0 with my Samsung TV browser.

STR:
1. Load https://air.mozilla.org/authentication/signin/
2. Click the page's "Sign In" button.
3. Click the Auth0 login widget's "Login with Google" or "Login with GitHub" button.

RESULT:
The browser is redirected to auth.mozilla.auth0.com and shows the following error message: "400 Bad Request. The SSL certificate error. nginx"

I loaded a different website that uses a Let's Encrypt cert and it didn't show any cert errors, so this error does not appear to be that the Let's Encrypt root cert is untrusted.

My Samsung TV and Windows desktop have the same public IP address (67.188.162.191) so there does not appear to be a Samsung proxy server between my TV browser and the web.

My TV browser's User-Agent string is:

Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) SamsungBrowser/1.1 TV Safari/538.1
I've opened a ticket on auth0 side to look at the nginx 400 error on auth.mozilla.auth0.com as well:
https://support.auth0.com/tickets/17696 (this is a private issue, I'm putting this here for reference)
I believe this may be fixed. The server was incorrectly sending a client certificate request, that is handled differently by different clients. Normally, reply is optional, but not necessarily.

The client response in this case also caused a 400 error on the nginx side, as while it requested a certificate it did not expect one back.

Can you re-test and confirm ?
(also pinged on IRC)
Assignee: infra → gdestuynder
Status: NEW → ASSIGNED
Flags: needinfo?(cpeterson)
From IRC: cpeterson | \o/ it worked!

Closing on your behalf. It was fixed by disabling the option server-side.

Thanks!
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(cpeterson)
Resolution: --- → FIXED
(Reporter)

Comment 4

2 years ago
Yes. I can successfully log in now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.