Facing issue with SHA256 Security Algorithm
facing issue with the SHA256 Security Algorithm, where the Digest Algorithm is being sent as SHA1 instead of SHA256,
In Security profile, the outflow signature method selected as RSA_SHA256, the digest method was SHA_1 instead of SHA_256
HCA Healthcare
US
Set the digest to SHA-256 in your WS-Security profile, not just the signature. Open the security profile rule, go to Outbound settings, and change Digest method from SHA-1 to SHA-256, then save. Check the Connect SOAP rule and make sure it references this same profile and does not override the digest in a custom policy. If you use a custom WS-Policy, update the XML to <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> and <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>. Confirm your signing certificate/keystore supports SHA-256 (most do) and isn’t pinned to SHA-1. Clear the rule cache/restart the node or at least re-save the connector to pick up changes. Re-test and inspect the SOAP header to verify the DigestMethod element shows sha256. If it still shows SHA-1, search for any legacy “policy fragment” or data transform that sets the Algorithm attribute directly. Finally, align with the service provider’s policy to ensure both signature and digest are SHA-256.