RichardD012
commented
5 years ago Not sure if this is correct but changing the constructor of RsaCryptoServiceProviderProxy.cs seems to work. Again, not familiar enough with this code base but it def works.
public RSACryptoServiceProviderProxy(RSACryptoServiceProvider rsa)
{
if (rsa == null)
throw LogHelper.LogArgumentNullException(nameof(rsa));
// Level up the provider type only if:
// 1. it is PROV_RSA_FULL or PROV_RSA_SCHANNEL which denote CSPs that only understand Sha1 algorithms
// 2. it is not associated with a hardware key
#if WINDOWS
if ((rsa.CspKeyContainerInfo.ProviderType == PROV_RSA_FULL || rsa.CspKeyContainerInfo.ProviderType == PROV_RSA_SCHANNEL) && !rsa.CspKeyContainerInfo.HardwareDevice)
{
var csp = new CspParameters();
csp.ProviderType = PROV_RSA_AES;
csp.KeyContainerName = rsa.CspKeyContainerInfo.KeyContainerName;
csp.KeyNumber = (int)rsa.CspKeyContainerInfo.KeyNumber;
if (rsa.CspKeyContainerInfo.MachineKeyStore)
csp.Flags = CspProviderFlags.UseMachineKeyStore;
// If UseExistingKey is not specified, the CLR will generate a key for a non-existent group.
// With this flag, a CryptographicException is thrown instead.
csp.Flags |= CspProviderFlags.UseExistingKey;
_rsa = new RSACryptoServiceProvider(csp);
// since we created a new RsaCryptoServiceProvider we need to dispose it
_disposeRsa = true;
}
else
{
// no work-around necessary
_rsa = rsa;
}
#else
_rsa = rsa;
#endif
}Another thing I noticed when building in OSX, JsonWebKey fails to build because once the statement is built you get unreachable code. It ultimately becomes:
internal ECDsa CreateECDsa(string algorithm, bool usePrivateKey)
{
throw new NotImplementedException(LogMessages.IDX10676);
if (Crv == null)
throw LogHelper.LogArgumentNullException(nameof(Crv));
if (X == null)
throw LogHelper.LogArgumentNullException(nameof(X));
if (Y == null)
throw LogHelper.LogArgumentNullException(nameof(Y));
...
}
brentschmaltz
ghost
CheloXL
af-mst
GeoK
mikesig
pauloofmeta
When creating a new
JwtSecurityTokenHandler()and passing in aRSACryptoServiceProviderin OSX, an exception is thrown when callingValidateToken.The error is:
System.PlatformNotSupportedException: 'CspKeyContainerInfo' requires Windows Cryptographic API (CAPI), which is not available on this platform.The stack-trace refers to
RsaCryptoServiceProviderProxy.csand looking at the commit history, it looks like it added Net Standard 2.0 Support. The parameter references theCspKeyContainerInfoin the constructor here.This does not work in OSX as, as the exception states, CspKeyContainerInfo isn't supported. So when it tries to access the parameter, this exception is thrown. The code used to call this previously worked in 5.2.4.