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.

Sign up for GitHub

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

Jump to bottom

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

Closed
jennyf19 opened this issue Jun 15, 2021 · 1 comment
Closed

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

jennyf19 opened this issue Jun 15, 2021 · 1 comment
Labels
fixed P1
Milestone
1.13.1

Comments

@jennyf19
Copy link
Collaborator

jennyf19 commented Jun 15, 2021 •
edited by jmprieur
Loading

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).
@jennyf19 jennyf19 added this to the 1.13.1 milestone Jun 15, 2021
@jennyf19 jennyf19 mentioned this issue Jun 15, 2021
Merged
@jennyf19
Copy link
Collaborator Author

fixed in 1.13.1

@pmaytak pmaytak mentioned this issue Aug 30, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed P1
Projects
None yet
Milestone
1.13.1
Development

No branches or pull requests
1 participant
@jennyf19