Skip to content

[Feature Request] MSAL/IdWeb blocks FMI scenarios with a distributed cache #5199

@trwalke

Description

@trwalke

MSAL client type

Confidential

Problem statement

MSAL needs to provide a mechanism to discourage customers from performing FMI scenarios with a distributed cache as it can lead to security issues.
See how-to-use-fmi-tokens.md - Repos for token caching issues.

Proposed solution

MSAL can provide a signal in the token cache notification args which are available to higher level apis to detect when customers have configured token cache serialization for IDistributedCache when the FMI node client id :urn:microsoft:identity:fmi is configured.

IdWeb throws an exception when it detects NoDistributedCacheUseReason from the TokenCacheNotificationArgs is not null and the distributed cache is configured.

Alternatives

No response

Metadata

Metadata

Assignees

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions