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).
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.
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)
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)
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
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?
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
Chetan Sarode
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
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.
bullpit
All-Star
21838 Points
4822 Posts
Active Directory or WindowsSAM support for TimeTracker starter kit
Sep 29, 2008 03:32 PM|LINK
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:
Thanks,Max
Max
Let Me Google That For You!
chetan.sarod...
All-Star
65619 Points
11118 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Sep 30, 2008 03:27 AM|LINK
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
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bullpit
All-Star
21838 Points
4822 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Sep 30, 2008 12:11 PM|LINK
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.
Max
Let Me Google That For You!
chetan.sarod...
All-Star
65619 Points
11118 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 01, 2008 03:31 AM|LINK
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
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bullpit
All-Star
21838 Points
4822 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 01, 2008 12:05 PM|LINK
Did you read what I posted?
Max
Let Me Google That For You!
chetan.sarod...
All-Star
65619 Points
11118 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 03, 2008 03:24 AM|LINK
Yes I read the post
What I am tryting to say is have to tried what I provided to you
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bullpit
All-Star
21838 Points
4822 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 03, 2008 12:44 PM|LINK
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?
Max
Let Me Google That For You!
chetan.sarod...
All-Star
65619 Points
11118 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 06, 2008 03:19 AM|LINK
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
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bullpit
All-Star
21838 Points
4822 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 06, 2008 12:44 PM|LINK
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.
Max
Let Me Google That For You!
chetan.sarod...
All-Star
65619 Points
11118 Posts
Re: Active Directory or WindowsSAM support for TimeTracker starter kit
Oct 07, 2008 03:28 AM|LINK
I will search and post it
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.