none
Issue in Live but not in Test - WCF related

    Soru

  • Hi

    I am not a developer but seeking help with the following which is preventing deployment to client and no-one seems to be able to fix it

    Same code works in TEST environment but when deployed to LIVE users cannot be authenticated and the following error message is displayed - see below

    Infrastructure supplier thinks it is a mistake by developers in deployment to live and developers think it is due to TEST and LIVE environments not being identical. Spent three months testing new system and now cant get it running in LIVE - can anyone help?   

    The request for security token could not be satisfied because authentication failed.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ServiceModel.FaultException: The request for security token could not be satisfied because authentication failed.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


    Stack Trace:

    [FaultException: The request for security token could not be satisfied because authentication failed.]

       System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target) +8751427

       System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState) +203

    [SecurityNegotiationException: The caller was not authenticated by the service.]

       System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +4767763

       System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +1725

       CharitiesTrust.Data.UsersService.IUserService.GetUserByUserName(User& User, String UserName1, String UserName2, String Password) +0

       CharitiesTrust.Data.UsersService.UserServiceClient.GetUserByUserName(User& User, String UserName1, String UserName2, String Password) in D:\Projects\CharitiesTrust\Main\CharitiesTrust.Data\Service References\UsersService\Reference.cs:941

       CharitiesTrust.BLL.UserManager.ValidateUser(String userName1, String userName2, String password) in D:\Projects\CharitiesTrust\Main\CharitiesTrust.BLL\UserManager.cs:250

       CharitiesTrust.Web.usercontrols.Login.btnLogin_Click(Object sender, EventArgs e) +657

       System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +154

       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3691

    13 Mart 2012 Salı 00:13

Yanıtlar

  • You'll have to supply more information:

       1. Binding

       2. IIS, Windows Service, Console app (Where does the service live)

       3. BindingConfiguration

       4. Authentication Type

       5. Service Behaviors

       6. Windows authentication? (Domain or Workgroup)

    If you are concern about privacy then make changes to the critical values before posting  

    There's a negotiation problem where there may be a mismatch in credentials 

    I can see that in your trace

    [SecurityNegotiationException: The caller was not authenticated by the service.]

    • Düzenleyen Dragan Radovac 13 Mart 2012 Salı 02:24
    • Yanıt Olarak İşaretleyen Yi-Lun Luo 19 Mart 2012 Pazartesi 12:17
    13 Mart 2012 Salı 02:22

Tüm Yanıtlar

  • You'll have to supply more information:

       1. Binding

       2. IIS, Windows Service, Console app (Where does the service live)

       3. BindingConfiguration

       4. Authentication Type

       5. Service Behaviors

       6. Windows authentication? (Domain or Workgroup)

    If you are concern about privacy then make changes to the critical values before posting  

    There's a negotiation problem where there may be a mismatch in credentials 

    I can see that in your trace

    [SecurityNegotiationException: The caller was not authenticated by the service.]

    • Düzenleyen Dragan Radovac 13 Mart 2012 Salı 02:24
    • Yanıt Olarak İşaretleyen Yi-Lun Luo 19 Mart 2012 Pazartesi 12:17
    13 Mart 2012 Salı 02:22
  • Hi

    thank you for reply - I will refer your response to the developers and infrastructure teams I am working with  - hopefully it will help them diagnose the problem - or they can provide more information and seek further assistance - thanks again

    Debby

    13 Mart 2012 Salı 12:52