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

[Documentation] Clarify status of System.IdentityModel.Tokens.Jwt #2542

Open
1 of 5 tasks
dosolkowski-work opened this issue Mar 27, 2024 · 0 comments
Open
1 of 5 tasks
Labels
IdentityModel8x Future breaking issues/features for IdentityModel 8x

Comments

@dosolkowski-work
Copy link

Documentation related to component

System.IdentityModel.Tokens.Jwt

Please check all that apply

  • typo
  • documentation doesn't exist
  • documentation needs clarification
  • error(s) in the example
  • needs an example

Description of the issue

The System.IdentityModel.Tokens.Jwt package says in its description that it is legacy and should be replaced. However, the very latest version of Microsoft.IdentityModel.Protocols.OpenIdConnect in this same repository still depends on it. It's very confusing for you to deprecate a package that you yourselves are still actively using, so it would be helpful to get some clarity and consistency on this.

Additionally, the suggested replacement of Microsoft.IdentityModel.JsonWebTokens doesn't seem to have the vast majority of the functionality of System.IdentityModel.Tokens.Jwt; there doesn't seem to be any support for actually creating tokens, because all the methods just take a string for the payload. Is there a different suggested replacement for this functionality, or do we get to just roll our own now?

@brentschmaltz brentschmaltz added the IdentityModel8x Future breaking issues/features for IdentityModel 8x label Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IdentityModel8x Future breaking issues/features for IdentityModel 8x
Projects
None yet
Development

No branches or pull requests

2 participants