Skip to content
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.

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

[Bug] CCS routing hint sends "missing from token response" as UPN in case of B2C #2748

Closed
jennyf19 opened this issue Jul 6, 2021 · 1 comment · Fixed by #3036
Closed
Assignees
Milestone

Comments

@jennyf19
Copy link
Collaborator

jennyf19 commented Jul 6, 2021

image
repro:
Sign-in w/a b2c account. Close the app. Sign-in again using .WithLoginHint(), and you'll see "Missing from the token response" in the UI, then in the routing hint, it is sent. Probably should not send it in this case? Or not send for B2C.

@trwalke
Copy link
Member

trwalke commented Jul 7, 2021

Yes, probably should not send. Thanks for finding @jennyf19

@trwalke trwalke added this to the 4.35.0 milestone Jul 7, 2021
@pmaytak pmaytak modified the milestones: 4.35.0, 4.36.0 Jul 27, 2021
@pmaytak pmaytak modified the milestones: 4.36.0, 4.37.0 Aug 31, 2021
@pmaytak pmaytak modified the milestones: 4.37.0, 4.38.0 Oct 23, 2021
@trwalke trwalke modified the milestones: 4.38.0, 4.39.0 Nov 19, 2021
gladjohn pushed a commit that referenced this issue Nov 24, 2021
… UPN in case of B2C #2748

Fixed by not adding CCS header if AuthorityType is B2C
gladjohn added a commit that referenced this issue Nov 29, 2021
* Fix for [Bug] CCS routing hint sends "missing from token response" as UPN in case of B2C #2748

Fixed by not adding CCS header if AuthorityType is B2C
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants