locked
How to fix below service error after login to application ? RRS feed

  • Question

  • User-147238865 posted

    Hi Experts,

    I am facing Issue that while browsing my service it's redrecting to login page (which is correct) but once i am giving user id and password and click on login it showing below error message,

    Server Error in '/STS' Application.

    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.

    I have already google this error and get a result as,

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/e23fe0fe-4143-4a7a-b9c4-38528ed07c51/the-header-security-error?forum=wcf

    https://forums.asp.net/t/2013068.aspx?Header+security+error+message+in+WCF+client

    but none of the results works for me, still geting same error message.

    Can anybody help me to resolve this error.

    Thanks lot for yuur help.

    SK.

    Monday, October 1, 2018 2:23 PM

Answers

  • User-330142929 posted

    Hi Surya_tech,

    It seems that the way client-side and server-side verify the credentials is inconsistent. How do you authenticate the client-side on the server-side? as you know, there are many ways for authenticating the client, X509 certificate, windows credentials, username/password. Security Token. The client should provide the corresponding authentication method in order to be verified by the server.

    If you use the SecurityTokenService to authenticate client credential, here is an official tutorial with some demos.

    https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-3.5/ms751517(v%3dvs.90)

    I suggest you post more details about the authentication configuration between the client-side and server-side so that I could give you an effective reply.

    Best Regards

    Abraham

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, October 22, 2018 7:15 AM
  • User-147238865 posted

    Hi,

    This issue is not in configuration file,the issue due to different ssl certificate install on my server.

    When you get this type of error, always keep in mind that either you have set the URL incorrectly for ssl or else certificate issue.

    Now this issue got resolved for me by checking the above things.

    Thanks,

    Sk.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, November 28, 2018 9:03 AM

All replies

  • User475983607 posted

    The error is telling you that the client configuration does not match the WCF service configuration.   It's up to you to fix the configuration as we have no idea how your services are deigned to function and we cannot see the code or configuration. 

    Monday, October 1, 2018 2:40 PM
  • User-330142929 posted

    Hi Surya_tech,

    It seems that the way client-side and server-side verify the credentials is inconsistent. How do you authenticate the client-side on the server-side? as you know, there are many ways for authenticating the client, X509 certificate, windows credentials, username/password. Security Token. The client should provide the corresponding authentication method in order to be verified by the server.

    If you use the SecurityTokenService to authenticate client credential, here is an official tutorial with some demos.

    https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-3.5/ms751517(v%3dvs.90)

    I suggest you post more details about the authentication configuration between the client-side and server-side so that I could give you an effective reply.

    Best Regards

    Abraham

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, October 22, 2018 7:15 AM
  • User-147238865 posted

    Hi,

    This issue is not in configuration file,the issue due to different ssl certificate install on my server.

    When you get this type of error, always keep in mind that either you have set the URL incorrectly for ssl or else certificate issue.

    Now this issue got resolved for me by checking the above things.

    Thanks,

    Sk.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, November 28, 2018 9:03 AM