I believe the earlier version of TT starter kit used to support active directory as UserAccoutStore. I downloaded the latest version and it has been stripped down to just Forms based authentication. Why is that? The remnants of that support are still there in the new version but no support. I can see the following which is of no use:

<!-- Define the location of the user account 
 0 = WindowsSAM
 1 = ActiveDirectory
 2 = None
-->
<add key="UserAccountSource" value="WindowsSAM" />

Can someone please tell me what all will be required to make it support Active Directory or if the support is still available, how can I get it.

PS: Please do not post on how to enable Active Directory authentication instead of Forms Authencation in Web.config file. 
It will take more than that as many tables in SQL Server are related with UserIds (GUID).

Hey read through this short article about active directory membership provider:

http://blogs.msdn.com/gduthie/archive/2005/08/17/452905.aspx

There you see several entries for the web.config file. Just switch them with you <membership> section you will see. That should be enough update your web.config file of timetracker. 

http://www.15seconds.com/issue/020730.htm

http://forums.asp.net/t/1263125.aspx

http://forums.asp.net/t/1105724.aspx

Thanks for your reponse Chetan and I really appreciate it. Please see the PS section of my post. I know how to use Active Directory as an authentication store. If you have gone thru the TT starter kit, you will know that it's not as simple as changing the web.config to make it work. There are a number of stored procedures working on several tables that use UserID (a GUID) which is generated when the users are created in ASPNETDB. When the authenticaion store changes to Active Directory, these stored procedures and table relations won't work. 

ASP.NET 2.0 ships with built-in role manager providers that work against SQL Express, SQL Server, and Active Directory (which can also be used against ADAM stores)

http://msdn.microsoft.com/en-us/library/ms998314.aspx

chetan.sarode:

ASP.NET 2.0 ships with built-in role manager providers that work against SQL Express, SQL Server, and Active Directory (which can also be used against ADAM stores)

http://msdn.microsoft.com/en-us/library/ms998314.aspx

Did you read what I posted?

If you have gone thru the TT starter kit, you will know that it's not as simple as changing the web.config to make it work. There are a number of stored procedures working on several tables that use UserID (a GUID) which is generated when the users are created in ASPNETDB. When the authenticaion store changes to Active Directory, these stored procedures and table relations won't work

Yes I read the post

What I am tryting to say is have to tried what I provided to you

chetan.sarode:

Yes I read the post

What I am tryting to say is have to tried what I provided to you

We are going in circles. All the links that you posted show how to use Active Directory with ASP.NET. I have no problems using Active Directory with ASP.NET. What I am looking for is what all to change in the application code, stored procedures and tables to make it all work. 

And a quick question:

Have you seen the ASP.NET TimeTracker Starter kit, I mean at the code and database level?

Yes, I have seen TTS at code & DB level

But I never tried with ACtive Directory, I want to ask one question what kind of error you are getting while runnig it, as you know how to use Active Directory with ASP.NET

I am not getting any error. I am not at an implementation level right now. I know how to implement Active Directory authentication. I am only talking about the design. The application for now uses ASPNETDB in SQL Server as an authentication store. What that means is that it uses the user data (specifically GUID) to apply roles, maintain all the timeentries, projects etc. The front end sends the logged in user name which is then used to pull the guid from the table and then used in all other stored proecdures and tables specific to the TT application.

Now when I will be using AD, the authentication store will change and obviously the ASPNETDB tables that were being used in the application specific stored procedures cannot be used. I would have to change all the stored procedures to not use GUID and possibly use just the user name sent from the front end.

What I am looking for is that if someone has already done this, or if the older version is available that used AD as authentication store, what were the steps taken and where all the change is required. Since there are different layes involved here, I want to be sure the code doesn't break when users are using it.

I will search and post it

Thanks a lot.

Look this thread if it helps you

http://forums.asp.net/t/1105724.aspx

Any updates on this

Not yet.

Ok, Please update the thread when u find some new research on it.