Oauth2 authentication protocol does not honors the defined port number in redirect URL in QGIS 3.22.1 (win10/ubuntu20.04)

[Bastiaandupon]

What is the bug or the crash?

When i configure the Oauth2 authentication panel. Its seems to redirect with the wrong port number like http://127.0.0.1:0 instead of http://127.0.0.1:7070
This issue does not occur on my test machine Qgis 3.16.14 (win10)

Steps to reproduce the issue

1. make a wfs layer: https://api.data.amsterdam.nl/v1/wfs/leidingeninfrastructuur/
   
2. configure the Oauth2 authentication panel with these urls: (see screenshot)
   https://iam.amsterdam.nl/auth/realms/datapunt-ad/protocol/openid-connect/auth
   https://iam.amsterdam.nl/auth/realms/datapunt-ad/protocol/openid-connect/token
3. when trying to connect, you get a redirect url error...

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

QGIS version	3.22.1-Białowieża	QGIS code revision	663dcf8
Qt version	5.12.8
Python version	3.8.10
GDAL/OGR version	3.3.2
PROJ version	7.2.1
EPSG Registry database version	v10.008 (2020-12-16)
GEOS version	3.9.1-CAPI-1.14.2
SQLite version	3.31.1
PDAL version	2.2.0
PostgreSQL client version	12.9 (Ubuntu 12.9-0ubuntu0.20.04.1)
SpatiaLite version	5.0.0
QWT version	6.1.4
QScintilla2 version	2.11.2
OS version	Ubuntu 20.04.3 LTS
Active Python plugins
MemoryLayerSaver	4.0.4
pdokbaggeocoder	0.6.6
qgis-maptiler-plugin	2.0.0
DataPlotly	3.8.1
BoundingBox	2.1
CityJSON-loader	0.7.2
mapswipetool_plugin	1.2
db-style-manager	0.8
monokai	1.0
processing_r	3.1.0
nominatim_locator_filter	0.2.4
pdokservicesplugin	3.7.2
grassprovider	2.12.99
db_manager	0.1.20
MetaSearch	0.3.5
processing	2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[elpaso]

Cannot reproduce on current master/linux.

Can you try a more recent version of QGIS or a nightly?

[Bastiaandupon]

@elpaso Yes I have tried, the bug doesn't exists anymore! I have noticed there was a lot of work going on the authentication protocols upstream. So you can close this bug now.