Question

I have setup a basic application which uses the ActiveDirectoryMembershipProvider to talk to our AD and authenticate users. It’s a simple login page with the control which redirects me to a simple output of who is logged in and associated ticket information, this works great and when I test it on my development machine it just works.

However if I deploy this to the webserver under a virtual directory, it simple refuses to direct or even acknowledge that there ticket is a valid ticket, it just refreshes back to the login page. If I type in rubbish credentials it actually recognises this and tells me there’;s an error, but if I login successfully it just refreshes the page. When I manually go the information page it treats me as an unauthenticated user!

This is most puzzling! Any help would be greatly appreciated!

Thanks

Jon

As requested a section of the Web.config

<connectionStrings>
  <add name="ActiveDirectory" connectionString="LDAP://x.x.x.117:389/OU=Users,DC=BC,DC=Local"/>
</connectionStrings>

<membership defaultProvider="ADMembershipProvider">
<providers>

<add name="ADMembershipProvider" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ActiveDirectory" connectionUsername="xxxxxx" connectionPassword="xxxxxxx" attributeMapUsername="sAMAccountName" applicationName="/"/>

</providers>

</membership>

Answer 1

<forms slidingExpiration="true" **path="/Search"** name=".ADAuthCookie" timeout="10"/>

It was also helpful to include a ‘path’ attribute!!!!

Jon