locked
error authenticating in Active Directory using Membership Provider RRS feed

  • Question

  • User-1414681527 posted

    Greetings.

    I have an ASP application that is designed to authenticate users through Membership Provider against a corporate Active Directory. It worked just fine in our development/test environment but when we deployed it to client’s environment we got this error:

     

    Unable to establish secure connection with the server (C:\Inetpub\Console\web.config line 77)
    
       at System.Web.Configuration.ProvidersHelper.InstantiateProvider(ProviderSettings providerSettings, Type providerType)
    
       at System.Web.Configuration.ProvidersHelper.InstantiateProviders(ProviderSettingsCollection configProviders, ProviderCollection providers, Type providerType)
       at System.Web.Security.Membership.Initialize()
       at System.Web.Security.Membership.ValidateUser(String username, String password)
       at ConsoleManglar.Services.LogIn(User user) in C:\Documents and Settings\Administrator.MANGLAR\My Documents\Visual Studio 2008\Projects\ConsoleManglar\Services.svc.cs:line 131
       at SyncInvokeLogIn(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)


    In the same server there are several .NET applications that attempt to connect directly to the Active Directory (not using ASP’s Membership Provider) and they succeed, so we can assert that the Active Directory is alive and the regular connection is working.

    Our best hypothesis so far is that the Active Directory is demanding some sort of secure connection for authentication requests from Membership Provider.

    Any ideas? Does this make any sense for you?

    Thanks in advance

    Monday, May 24, 2010 1:28 PM

All replies