fix: allow non-HTTP URIs in OAuth2 provider redirect URIs #18880
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.
Changed OAuth2 redirect URI validation to accept custom URI schemes
This PR updates the validation for OAuth2 provider app redirect URIs to use the more flexible
uri
validator instead of the stricterhttp_url
validator. This allows for custom URI schemes that don't follow reverse domain notation, while still blocking well-known schemes like http, https, ftp, etc.The change removes the requirement that custom schemes must contain a period, making the validation more permissive for various client applications while maintaining security by continuing to block well-known schemes.