-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
-
Fix Version/s: 7.1.10 DXP FP25, 7.1.X, 7.2.10 DXP FP14, 7.2.10.5 DXP SP5, 7.2.X, 7.3.10 DXP FP1, 7.3.10.1 DXP SP1, 7.3.6 CE GA7, 7.4.13 DXP GA1, Master
-
Component/s: Application Security > OpenID Connect
-
Branch Version/s:7.3.x, 7.2.x, 7.1.x
-
Backported to Branch:Committed
-
Story Points:5
-
Sprint:AppSec Iteration 56
-
Git Pull Request:
The user is not able to login using OpenID Connect configured with Microsoft Azure because default timeout connection it may be long enough.
Steps to reproduce:
- Configure an OpenID Connect Provider with Microsoft Azure
- Go to Control Panel -> Configuration -> System Settings -> SSO -> OpenID Connect Provider and add a new configuration (at the moment of this ticket creation we have a test environment available here)
- On Control Panel -> Configuration -> System Settings -> SSO -> OpenID Connect check Enabled and save
- Try to login using Open ID
Expected behavior:
User can log in
Actual behavior
User get an Error
More info:
- Comments on: LPS-127037
- Comments on: LPSP-402
—
To solve this issue, a new property has been added in the Configuration: SSO - OpenID Connect Provider: Token Connection Timeout in Milliseconds, it sets the amount of time to wait (in milliseconds) when establishing a connection to validate the token before timing out; we have set 1000ms as default to avoid this problem.
- fixes
-
LPS-132369 Cannot login using OpenID Connect: Timeout error
-
- Completed
-
- relates
-
LPS-134142 OpenIdConnect getter: Fix typo
- Closed
- split from
-
LPS-127037 Error when using OpenID Connect to request userinfo from Azure
- Closed