feat: Increase BackchannelTimeout to 120 seconds for Okta communications #277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes the issue #273
This pull request increases the default
BackchannelTimeout
value inOktaWebOptions
from 60 seconds to 120 seconds. This change addresses intermittent timeout issues reported when calling the/userinfo
endpoint during the OpenID Connect authentication flow.Why is this change necessary?
The
/userinfo
endpoint is critical for retrieving additional claims about the authenticated user. These claims may not be included in the ID token but are often required for authorization or user profile completeness. Increasing the timeout ensures that transient network delays or server-side slowness do not disrupt the authentication flow.Changes Made
BackchannelTimeout
property inOktaWebOptions
to 120 seconds.Testing
/userinfo
endpoint.Notes
While this change reduces the likelihood of timeouts, it is recommended to monitor network conditions and ensure that the
/userinfo
endpoint is reachable with minimal latency.