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] In web api scenario, use the tid claim of the incoming assertion #1738

Closed
1 of 8 tasks
bgavrilMS opened this issue May 24, 2022 · 2 comments
Closed
1 of 8 tasks
Labels
bug Something isn't working P2
Milestone

Comments

@bgavrilMS
Copy link
Member

Which version of Microsoft Identity Web are you using?
Note that to get help, you need to run the latest version.

Where is the issue?

  • Web app
    • Sign-in users
    • Sign-in users and call web APIs
  • Web API
    • Protected web APIs (validating tokens)
    • Protected web APIs (validating scopes)
    • Protected web APIs call downstream web APIs
  • Token cache serialization
    • In-memory caches
    • Session caches
    • Distributed caches
  • Other (please describe)

In a multi-tenanted web api, IdWeb should acquire the OBO token using a tenanted authority, where the tenant is the tid claim of the incoming assertion (i.e. it should not use common)

@bgavrilMS bgavrilMS added bug Something isn't working P2 labels May 24, 2022
@jmprieur
Copy link
Collaborator

Proposed design:

add an else condition taking the user.GetTenantId()

if (!string.IsNullOrEmpty(tenantId))
{
builder.WithTenantId(tenantId);
}

@jennyf19 jennyf19 mentioned this issue Jun 1, 2022
@jennyf19
Copy link
Collaborator

jennyf19 commented Jun 4, 2022

Included in 1.25.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2
Projects
None yet
Development

No branches or pull requests

3 participants