Change SHA1 to other algorithm as default signature digest

Products

• CA API Gateway

Issue/Introduction

Are there ways to enable SHA256 or others algorithm in the 'Create SAML Token' or in the 'Build SAML Protocol Response'? Or is there an option to make SHA-256 as default signature digest for (Non-soap) Sign XML Element assertion and Build SAML Protocol Response assertions? 
We are facing an issue building SAML responses with GWs, because there is only the SHA1 option and it is deprecated.

When use the default algorithm, the "(Non-SOAP) Sign XML Element" assertion could cause the backen throwing "digest is invalid because the computed digest differs from the digest in the XML."  When consuming the XML. 

Environment

Release : 10.x

Component :

Resolution

Setting CWP "wss.decorator.digsig.messagedigest" to SHA-256 changed the response algorithms accordingly