CX_WS_SECURITY_FAULT when checking configuration

[guillaume_bouzebra]

When we run the duetconfig.exe /checkconfiguration (or run the SharePoint job to sync SAP roles) we receive the following exception:

An exception occurred: Invalid algorithm (expected http://www.w3.org/2001/04/xmldsig-more#rsa-sha256, received http://www.w3.org/2001/04/xmldsig-more#hmac-sha256)

And in SOAMANAGER traces we have:

CX_WS_SECURITY_FAULT : An exception occurred: Invalid algorithm (expected http://www.w3.org/2001/04/xmldsig-more#rsa-sha256, received http://www.w3.org/2001/04/xmldsig-more#hmac-sha256) | program: CL_ST_CRYPTO==================CP include: CL_ST_CRYPTO==================CM00C line: 104

It's a new system that we are currently setting up.

Any help or idea are welcome...

[Former Member · Accepted solution]

Hi,

first of all can you please open any of the BDC models that you have imported to SharePoint. In the WcfMexDocumentUrl property you should find a URL that points to the WSDL of the service that is exposed on the SCL. Open this URL in a browser (you will have to provide the credentials to the SCL system) and look for the "AlgorithmSuite" which should be TripleDesSha256Rsa15 and the property "RequestSecurityTokenTemplate" which should be

KeyType: http://docs.oasis-open.org/ws-sx/ws-trust/200512/PublicKey

TokenType: http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1

If that is the case, then we have to further investiage. If this is not the case, then the security settings are not set correct in your SCL and we have to do some reconfiguration.

Regards,

Holger.

[Former Member · Accepted solution]

Hello Holger,

We are facing same Issue. SRTUTIL Error is

*Value An exception occurred: Invalid algorithm (expected http://www.w3.org/2001/04/xmldsig-more#rsa-sha256, received http://www.w3.org*

We checked following things.

first of all can you please open any of the BDC models that you have imported to SharePoint. In the WcfMexDocumentUrl property you should find a URL that points to the WSDL of the service that is exposed on the SCL. Open this URL in a browser (you will have to provide the credentials to the SCL system) and look for the "AlgorithmSuite" which should be TripleDesSha256Rsa15 and the property "RequestSecurityTokenTemplate" which should be

KeyType: http://docs.oasis-open.org/ws-sx/ws-trust/200512/PublicKey

TokenType: http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1

All above are in correct place please suggest. Please help how to proceed...

Regards

Shashanka

[guillaume_bouzebra]

Right, it was misconfigured. We have changed the algorithm, reactivated the profile (SOAMANAGER) then regenerated BDC models and imported again into SharePoint.

Thanks a lot for your help!