Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Feature Request] [M] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message #2358

Closed
bgavrilMS opened this issue Jan 22, 2021 · 1 comment · Fixed by #2505

Comments

@bgavrilMS
Copy link
Member

No description provided.

@bgavrilMS bgavrilMS added this to the 4.27.0 milestone Jan 22, 2021
@trwalke trwalke modified the milestones: 4.27.0, 4.28.0 Feb 19, 2021
@jmprieur
Copy link
Contributor

jmprieur commented Mar 3, 2021

@bgavrilMS
Let's make sure we take this one to ease the migration to WAM

@bgavrilMS bgavrilMS changed the title [Bug] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message [M] [Bug] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message Mar 4, 2021
@bgavrilMS bgavrilMS changed the title [M] [Bug] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message [Feature Request] [Bug] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message Mar 11, 2021
@bgavrilMS bgavrilMS changed the title [Feature Request] [Bug] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message [Feature Request] [M] When using WAM with incorrect redirect URI, MSAL should suggest the correct URI in the message Mar 11, 2021
@bgavrilMS bgavrilMS modified the milestones: 4.28.0, 4.29.0 Mar 18, 2021
@bgavrilMS bgavrilMS self-assigned this Mar 24, 2021
@bgavrilMS bgavrilMS linked a pull request Mar 24, 2021 that will close this issue
@bgavrilMS bgavrilMS reopened this Mar 25, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants