[Supportability Bug] Deprecate ClientAssertion(string) as it leads to assertion expiration issues

[Avery-Dunn]

MSAL client type

Confidential

Problem Statement

Creating a client assertion with just a String can easily lead to expiration issues.

Proposed solution

Deprecate the option to use a String, and instead recommend the callback option. This is also planned for other MSALs: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/4775 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/7118 https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/705

Alternatives

No response