Skip to content

[Bug] In web api scenario, use the tid claim of the incoming assertion #1738

Closed

Description

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)

Activity

  1. jmprieur commented on May 24, 2022

    @jmprieur
    Collaborator

    Proposed design:

    add an else condition taking the user.GetTenantId()

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

  2. jennyf19 commented on Jun 4, 2022

    @jennyf19
    Collaborator

    Included in 1.25.0 release

  3. added this to the 1.25.0 milestone on Jun 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions