Redirect Check

[codefiesta]

Description

Some providers (like Slack) can have multiple layers of authentication. For instance, to sign into Slack, you might first need to sign into Google or OKTA and then can proceed with exchanging a code for an authorization token. The OAWebViewCoordinator now checks to make sure we should actually try and exchange a code for a token by always checking if the url we are intercepting starts with the redirect uri first.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules