Director Login Issue - An unsecured or incorrectly secured fault was received


 

Product 

  
 Applies To 
  
 Product(s):Assetwise Director
 Version(s):16.8.xx 16.9.xx
 Environment: N/A
 Area: Login
 Subarea: 
 Original Author:Dennis Chan, Bentley Product Advantage Team

Problem Description:

User gets the following error when attempting to login to Assetwise Director:

  • An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.

    The header 'Security' from the namespace 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding.


    Exception Stack Trace:
    {
    --- Begin of exception stack trace ---
    System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: The header 'Security' from the namespace 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding.
    --- End of inner exception stack trace ---

Cause:

This is most likely caused by a version mismatch, meaning the Director version is different than the version on the application server being accessed.

Solution:

Un-install the mismatch version of Director from the client machine and Install the exact same version of Director to match the server's.

Workaround:

N/A