Skip to content

[Bug] When used with MISE, client certificates are not taken into account when calling downstream APIs in controllers #1583

Closed

Description

Which version of Microsoft Identity Web are you using?
1.21.1

Where is the issue?

  • Web API
    • [x ] Protected web APIs call downstream web APIs

Integrated with MISE

Repro
See Mise webApiCallGraph sample

Expected behavior
Client certificates are taken into account

Actual behavior
Neither cert or client secret

Additional context / logs / screenshots / link to code
The internal method EnableTokenAcquisition initializes the CcaOptions from the delegate, but not the MicrosoftIdentityOptions. However, the client certs are in MicrosoftIdentityOptions, not CcaOptions

The fix is easy. just bind the configuration with the mergeOptions (which have all the members of MicrosoftIdentityOptions)

Activity

  1. jmprieur commented on Jan 7, 2022

    @jmprieur
    CollaboratorAuthor

    As we are here, let's make sure that the configuration is an IConfigurationSection instead of an IConfiguration

  2. jennyf19 commented on Jan 8, 2022

    @jennyf19
    Collaborator
  3. added this to the 1.22.0 milestone on Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0bugSomething isn't workingfixed

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions