Skip to content

[Bug] LegacyCacheComp using cca options and not ms id options #1268

Closed

Description

@jennyf19

Repro steps:
Run a web app and web API without setting the LegacyCacheCompatibilityEnabled property in appsettings.json.

Expected
ADAL cache compatibility should be disabled by default

Actual
It's enabled

Analysis:
A regression was introduced with the multi-scheme work where the LegacyCacheCompatibilityEnabled value was taken from the ConfidentialClientApplicationOptions (default true), instead of the MicrosoftIdentityOptions (default false).

Activity

  1. added this to the 1.13.1 milestone on Jun 15, 2021
  2. jennyf19 commented on Jun 15, 2021

    @jennyf19
    CollaboratorAuthor

    fixed in 1.13.1

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

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions