Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Running FusionAuth in Docker with a port mapping like 2222:9011, the Identity Provider login redirecturi contained the wrong (internal) port from FusionAuth 1.37 through 1.45.x, so the IdP callback went to an unreachable URL and login failed. The redirecturi should have used the external mapped port (e.g. http://the local machine:2222/oauth2/callback). The bug persisted across every release from 1.37 until the 1.46.0 fix.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed in FusionAuth 1.46.0; the reporter verified the correct external port appears in redirect_uri and the redirect works on that image. Upgrade to 1.46.0 or newer if you run FusionAuth behind a Docker port mapping with Identity Provider login. The fix was verified against the exact Docker port-mapping setup from the report. Source: https://github.com/FusionAuth/fusionauth-issues/issues/2250