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

[Engineering task] Implement Claims API to Bypass Cache When Claims are Present in MSAL with Managed Identity #4845

Closed
gladjohn opened this issue Jul 17, 2024 · 2 comments · Fixed by #4875

Comments

@gladjohn
Copy link
Contributor

Task type

Development

Description

Currently, MSAL with Managed Identity does not expose any API claims API. With CAE (Continuous Access Evaluation) being enabled by default, we need to implement a mechanism to bypass the cache if claims are detected in the token request.

Steps to Reproduce:
Enable CAE by default in MSAL with Managed Identity.
Make a token request with claims present.

Observe that the cache is not bypassed, leading to potential stale token usage.

Expected Behavior:
When claims are present in the token request, the cache should be bypassed to ensure that the latest token is used, in line with CAE requirements.

Solution

Proposed Solution:

  1. Expose the claims API in MSAL for MI
  2. Expose Claims to MI Assertion Provider for FIC
@rayluo
Copy link
Contributor

rayluo commented Jul 18, 2024

Yes, bypassing cache shall be part of the CAE implementation.

Question. Do all the MI v1 endpoints support CAE now? If so, do they use a newer API version on the wire? And do all MSAL's MI v1 support CAE?

@bgavrilMS
Copy link
Member

Just bypass the cache for msi v1. @gladjohn will confirm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
3 participants