S
slegian-bva
Guest
Sort of, once we sorted out the working version and the mechanics. The certificate business made things a bit more complicated. MS seem to be still working on this, the API changed from 4.xx to 5.xx, the doco was not in sync, the samples were around 4.xx and the certificate business only worked in 5.xx Free code so can't complain... It turned out we need 2 assemblies - Microsoft.IdentityModel.Tokens, Version=5.2.2.0 and System.IdentityModel.Tokens.Jwt, Version=5.2.2.0 You then use the System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler:ValidateToken to get a yay/nay and a "Microsoft.IdentityModel.Tokens.SecurityToken" object which you can then cast to System.IdentityModel.Tokens.Jwt.JwtSecurityToken which is a nice JWT representation. I'll see if I can put up some sample code...
Continue reading...
Continue reading...