With Windows Identity Foundation (WIF) now integrated into .NET and the System.IdentityModel.Tokens.Jwt NuGet package getting 8,000+ downloads every day, I don't understand why there isn't any official documentation. The MSDN documentation is disgraceful, offering nothing that IntelliSense doesn't already communicate, what little you have on Microsoft Docs offers no instructions, and the official GitHub repo for the NuGet package is a confusing mess that feels like trying to crack a walnut with a sledgehammer when trying to sift through the many projects just to find a simple, no-frills example.
For example, take a standard and common use case of needing to encrypt a JWT payload. The only usable solution I could find is this Stack Overflow post, and even that uses a hodgepodge of WIF 3.5 and .NET 4+ namespaces that feels more like a hack than a good solution.
JWTs are the standard now, and Microsoft Docs desperately needs dedicated documentation for developers on this topic. Please let us know what the plan is for this.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
With Windows Identity Foundation (WIF) now integrated into .NET and the
System.IdentityModel.Tokens.JwtNuGet package getting 8,000+ downloads every day, I don't understand why there isn't any official documentation. The MSDN documentation is disgraceful, offering nothing that IntelliSense doesn't already communicate, what little you have on Microsoft Docs offers no instructions, and the official GitHub repo for the NuGet package is a confusing mess that feels like trying to crack a walnut with a sledgehammer when trying to sift through the many projects just to find a simple, no-frills example.For example, take a standard and common use case of needing to encrypt a JWT payload. The only usable solution I could find is this Stack Overflow post, and even that uses a hodgepodge of WIF 3.5 and .NET 4+ namespaces that feels more like a hack than a good solution.
JWTs are the standard now, and Microsoft Docs desperately needs dedicated documentation for developers on this topic. Please let us know what the plan is for this.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.