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

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

Open
Avery-Dunn opened this issue May 21, 2024 · 0 comments
Open

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

Avery-Dunn opened this issue May 21, 2024 · 0 comments
Labels
confidential-client For issues related to confidential client apps SDK-Consistency Items that deal with consistency between all MSALs Supportability For issues related to improving the customer support experience

Comments

@Avery-Dunn
Copy link
Collaborator

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:
AzureAD/microsoft-authentication-library-for-dotnet#4775
AzureAD/microsoft-authentication-library-for-js#7118
AzureAD/microsoft-authentication-library-for-python#705

Alternatives

No response
@Avery-Dunn Avery-Dunn added needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template Supportability For issues related to improving the customer support experience confidential-client For issues related to confidential client apps SDK-Consistency Items that deal with consistency between all MSALs and removed needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template labels May 21, 2024
@bgavrilMS bgavrilMS moved this to Features and lower priority fixes in MSAL Java Customer Trust May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
confidential-client For issues related to confidential client apps SDK-Consistency Items that deal with consistency between all MSALs Supportability For issues related to improving the customer support experience
Projects
MSAL Java Customer Trust
Status: Features and lower priority fixes
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Avery-Dunn