You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Documentation related to component
System.IdentityModel.Tokens.Jwt
Please check all that apply
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 ofMicrosoft.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 ofSystem.IdentityModel.Tokens.Jwt
; there doesn't seem to be any support for actually creating tokens, because all the methods just take astring
for the payload. Is there a different suggested replacement for this functionality, or do we get to just roll our own now?The text was updated successfully, but these errors were encountered: