Skip to content

B2C Redirect URI #2544

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task
zhangxAmtrak opened this issue Nov 4, 2020 · 3 comments
Closed
1 task

B2C Redirect URI #2544

zhangxAmtrak opened this issue Nov 4, 2020 · 3 comments
Labels
no-issue-activity Issue author has not responded in 5 days question Customer is asking for a clarification, use case or information.

Comments

@zhangxAmtrak
Copy link

#2113
Library

Description

Please provide your question here, including as much relevant details as possible.

"How do I resolve double redirect?"

We are implementing Azure B2C for company consumer site. The site is implemented as SPA angular application and has header "SIGN IN" button. The header is on every page that makes impossible to configure redirect uri from B2C portal. We had to use code below to redirect page to destination where the login is triggered. But that caused double redirect on client browser. Is there anyway we can avoid double redirect? Any suggestion?

redirectUri: "http://localhost:6420/",
navigateToLoginRequestUrl: true
@zhangxAmtrak zhangxAmtrak added the question Customer is asking for a clarification, use case or information. label Nov 4, 2020
@jasonnutter
Copy link
Contributor

Can you please clarify what you mean by "double redirect"? By design, when navigateToLoginRequestUrl is enabled, the browser will be redirected from B2C to your redirect URI (http://localhost:6420/), and then again from your redirect URI to the page the user was originally on when they triggered login.

Also, please update to the latest version of msal (1.4.3), and let us know if this is still an issue.

@github-actions
Copy link
Contributor

This issue has not seen activity in 14 days. It will be closed in 7 days if it remains stale.

@github-actions github-actions bot added the no-issue-activity Issue author has not responded in 5 days label Nov 19, 2020
@github-actions
Copy link
Contributor

This issue has been closed due to inactivity. If this has not been resolved please open a new issue. Thanks!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
no-issue-activity Issue author has not responded in 5 days question Customer is asking for a clarification, use case or information.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jasonnutter @zhangxAmtrak