OCES3 certificate not supported

[Kishmet]

If you use an OCES3 certificate for the clientCertificate you will encounter the following error from the framework:
"Unexpected error: Der er angivet en ugyldig algoritme." or "Invalid algoritme specified".

This error can be solved by modifying the code in the file:
Digst.OioIdws.OioWsTrust.Utils.XmlSignatureUtils.
Change the following line (in the SignDocument function):
signedXml.SigningKey = cert.PrivateKey;
To
signedXml.SigningKey = cert.GetRSAPrivateKey();

The stacktrace for the error:
Server stack trace:
ved System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
ved System.Security.Cryptography.Utils.SignValue(SafeKeyHandle hKey, Int32 keyNumber, Int32 calgKey, Int32 calgHash, Byte[] hash, Int32 cbHash, ObjectHandleOnStack retSignature)
ved System.Security.Cryptography.Utils.SignValue(SafeKeyHandle hKey, Int32 keyNumber, Int32 calgKey, Int32 calgHash, Byte[] hash)
ved System.Security.Cryptography.RSACryptoServiceProvider.SignHash(Byte[] rgbHash, Int32 calgHash)
ved System.Security.Cryptography.RSAPKCS1SignatureFormatter.CreateSignature(Byte[] rgbHash)
ved System.Security.Cryptography.AsymmetricSignatureFormatter.CreateSignature(HashAlgorithm hash)
ved System.Security.Cryptography.Xml.SignedXml.ComputeSignature()
ved Digst.OioIdws.OioWsTrust.Utils.XmlSignatureUtils.SignDocument(XDocument xDoc, IEnumerable`1 ids, X509Certificate2 cert)
ved Digst.OioIdws.OioWsTrust.ProtocolChannel.OioWsTrustMessageTransformer.SignMessage(XDocument& xDocument, X509Certificate2 clientCertificate)
ved Digst.OioIdws.OioWsTrust.ProtocolChannel.OioWsTrustMessageTransformer.ModifyMessageAccordingToStsNeeds(Message& request)
ved Digst.OioIdws.OioWsTrust.ProtocolChannel.OioWsTrustChannel.Request(Message message, TimeSpan timeout)
ved System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
ved System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
ved System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
ved System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
ved System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
ved System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
ved System.ServiceModel.Security.IWSTrustContract.Issue(Message message)
ved System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
ved System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst)
ved Digst.OioIdws.OioWsTrust.StsTokenService.GetToken(StsAuthenticationCase stsAuthenticationCase, SecurityToken authenticationToken)
2023-02-10 13:52:43,523 INFO OioIdws - Unexpected error: Der er angivet en ugyldig algoritme.

[mdbech]

Hi @Kishmet,

Are you aware of the fact that you might need to re-encrypt PKCS12 using 3DES before installing the certificate in Microsoft Crypto API? If you are using an old version of Windows then the PKCS12 will install no problem but you can't use the private key afterwards and no error are reported.

On the support website https://www.nemlog-in.dk/vejledningertiltestmiljo/ in the according titled "Test med OCES3 certifikater" this is explained. If you Danish is a little rusty then you can use the following two OpenSSL commands to re-encrypt the PKCS12

openssl pkcs12 -in <OCES3 PKCS12>.p12 -out <Temporary PEM file>.pem
openssl pkcs12 -keypbe PBE-SHA1-3DES -certpbe PBE-SHA1-3DES -export -in <Temporary PEM file>.pem -out <New OCES3 PKCS12>.p12 -name "<ALIAS>"
rm <Temporary PEM file>.pem

Please get back here if this does not resolve your problem.

Regards,
mdbech

[Kishmet]

We have multiple third party system providers who keep reporting this "Invalid signature algorithm"-error.
Based on the stacktraces and images provided, they are all using the code from this repository. The code is unmodified.
The used certificates are different, but they are all OCES3. Both Win10 and Win11 machines have been used for testing and result in the same error.

The SignDocument function seems to be out of date. The code in the red square does not work with OCES3, unless changed to "cert.GetRSAPrivateKey()".
The code in the green square does not seem to specify the correct algorithm, if compared to the public OCES2 vs. OCES3 documentation:

Why not update the code in this repository, so new OCES3 certificates are supported out of the box?