We\'re using IdentityServer3 and have been very happy with it so far.
We\'ve gotten to secure MVC and ASP.NET Web API applications very easily wi
I didn't get to solve this problem but Dominick Baier, one of the developers of IdentityServer, found a workaround.
He thinks the exception comes from a bug in WCF or an incompatibility between WCF and the JwtSecurityTokenHandler
. Since he considers WCF done, he doesn't expect someone to take a look at it.
His solution is to wrap the JWT token in a SAML token. Then, by subclassing SamlSecurityTokenHandler
, get it back and validate it against an instance of JwtSecurityTokenHandler
.
Here are the links:
Everybody have fun, now :-)