Closed Bug 1770802 Opened 3 years ago Closed 3 years ago

OAUTH2 login for gmail fails when something is already listening on localhost

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1748416

People

(Reporter: astrothayne, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0

Steps to reproduce:

I attempted to authenticate to a gmail using Oauth2.

I have a service listening on port 80 on localhost, which redirects to https.

Actual results:

After going through the redirect flow, the login dialog redirected to localhost, and since my local service redirected to https it redirected to https://localhost and I got a certificate error, because I don't have a certificate for the "localhost" domain (i have certificates for a custom domain).

After turning off my service that listens on port 80 I got it to work, although it took me a while to figure out what was happening, and someone less familiar with web technologies probably would have had an even harder time.

Expected results:

Oauth2 should have just worked.

Ideally thunderbird would dynamically detrmine an available port and use that, instead of port 80. If that isn't possible (for example because google requires using a specific origin), then at least use a port that is less likely to have a conflict.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.