|
|
You're in the
asp.net security
group:ADSI
asp.net security:
I have question about Active Directory. We have developed a site it has 75K users on SQL server 2005 associated with roles, now we are thinking to change it to Active directory is it good idea or bad idea? if it is good how to migrate it. Thanks in advance.
You haven't given us enough information about what you are doing to provide
you with a useful answer. In terms of size, 75K users is not really significant for AD from a size perspective. I wouldn't worry about that. Migration of users may be tricky, depending a great deal on how you have stored the users' passwords in SQL and whether your intent is for your users to have the same password they had before. Joe K. -- Joe Kaplan-MS MVP Directory Services Programming Co-author of "The .NET Developer's Guide to Directory Services Programming" http://www.directoryprogramming.net -- [quoted text, click to view] "Chris" <Chris@discussions.microsoft.com> wrote in message news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... > Hi All, > > I have question about Active Directory. We have developed a site it has > 75K > users on SQL server 2005 associated with roles, now we are thinking to > change > it to Active directory is it good idea or bad idea? if it is good how to > migrate it. > > Thanks in advance. > > Chris
Joe ,
Thanks for quick respone. We developed a site with public and privatre applications, for private applications user need to login those users paswwords we dont want to distrub, you are rite we want to use same passwords. Any kind of possible other solutions also welcome( there is no time constraint for development). Regards, Chris [quoted text, click to view] "Joe Kaplan" wrote:
> You haven't given us enough information about what you are doing to provide > you with a useful answer. In terms of size, 75K users is not really > significant for AD from a size perspective. I wouldn't worry about that. > > Migration of users may be tricky, depending a great deal on how you have > stored the users' passwords in SQL and whether your intent is for your users > to have the same password they had before. > > Joe K. > > -- > Joe Kaplan-MS MVP Directory Services Programming > Co-author of "The .NET Developer's Guide to Directory Services Programming" > http://www.directoryprogramming.net > -- > "Chris" <Chris@discussions.microsoft.com> wrote in message > news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... > > Hi All, > > > > I have question about Active Directory. We have developed a site it has > > 75K > > users on SQL server 2005 associated with roles, now we are thinking to > > change > > it to Active directory is it good idea or bad idea? if it is good how to > > migrate it. > > > > Thanks in advance. > > > > Chris > >
We are using username as firtsname.lastname password as plaintext. could you please provide me more information on using the SQL and AD membership providers for the integration with web application, how to implement it. aslo we want to use this AD for MOSS 2007, my question is do I need to have exchanger server for this to implementation, we are using this for government site. Regards, Chris [quoted text, click to view] "Joe Kaplan" wrote:
> Can you provide more details on how the passwords are stored in the SQL > database? If they are in plaintext or encrypted in a reversible format, > then you should be able to recover them and use them provision identities in > AD or ADAM such that the users will have the same username and password they > used in SQL. > > However, if they are in some sort of 1 way hash format, then it might be > very difficult to recover the plain text. That would make provisioning in > AD very difficult. > > Username format might be a bit of a problem as well, depending the formats > you allow in SQL. You would want those to be compatible with AD. ADAM > gives you a little more flexibility here. > > I definitely recommend that you try to use the SQL and AD membership > providers for the integration with your web application. They provide a > nice abstraction layer over the user store that makes it easier for your > application to not have to care where the users are stored. If you aren't > using the membership providers now, I recommend that as your first step. > > Joe K. > > -- > Joe Kaplan-MS MVP Directory Services Programming > Co-author of "The .NET Developer's Guide to Directory Services Programming" > http://www.directoryprogramming.net > -- > "Chris" <Chris@discussions.microsoft.com> wrote in message > news:FBDD0F3B-CA1F-4658-893F-6B760047043E@microsoft.com... > > Joe , > > > > Thanks for quick respone. > > > > We developed a site with public and privatre applications, for private > > applications user need to login those users paswwords we dont want to > > distrub, you are rite we want to use same passwords. > > > > Any kind of possible other solutions also welcome( there is no time > > constraint for development). > > > > Regards, > > Chris > > > > "Joe Kaplan" wrote: > > > >> You haven't given us enough information about what you are doing to > >> provide > >> you with a useful answer. In terms of size, 75K users is not really > >> significant for AD from a size perspective. I wouldn't worry about that. > >> > >> Migration of users may be tricky, depending a great deal on how you have > >> stored the users' passwords in SQL and whether your intent is for your > >> users > >> to have the same password they had before. > >> > >> Joe K. > >> > >> -- > >> Joe Kaplan-MS MVP Directory Services Programming > >> Co-author of "The .NET Developer's Guide to Directory Services > >> Programming" > >> http://www.directoryprogramming.net > >> -- > >> "Chris" <Chris@discussions.microsoft.com> wrote in message > >> news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... > >> > Hi All, > >> > > >> > I have question about Active Directory. We have developed a site it has > >> > 75K > >> > users on SQL server 2005 associated with roles, now we are thinking to > >> > change > >> > it to Active directory is it good idea or bad idea? if it is good how > >> > to > >> > migrate it. > >> > > >> > Thanks in advance. > >> > > >> > Chris > >> > >> > >> > >
Can you provide more details on how the passwords are stored in the SQL
database? If they are in plaintext or encrypted in a reversible format, then you should be able to recover them and use them provision identities in AD or ADAM such that the users will have the same username and password they used in SQL. However, if they are in some sort of 1 way hash format, then it might be very difficult to recover the plain text. That would make provisioning in AD very difficult. Username format might be a bit of a problem as well, depending the formats you allow in SQL. You would want those to be compatible with AD. ADAM gives you a little more flexibility here. I definitely recommend that you try to use the SQL and AD membership providers for the integration with your web application. They provide a nice abstraction layer over the user store that makes it easier for your application to not have to care where the users are stored. If you aren't using the membership providers now, I recommend that as your first step. Joe K. -- Joe Kaplan-MS MVP Directory Services Programming Co-author of "The .NET Developer's Guide to Directory Services Programming" http://www.directoryprogramming.net -- [quoted text, click to view] "Chris" <Chris@discussions.microsoft.com> wrote in message news:FBDD0F3B-CA1F-4658-893F-6B760047043E@microsoft.com... > Joe , > > Thanks for quick respone. > > We developed a site with public and privatre applications, for private > applications user need to login those users paswwords we dont want to > distrub, you are rite we want to use same passwords. > > Any kind of possible other solutions also welcome( there is no time > constraint for development). > > Regards, > Chris > > "Joe Kaplan" wrote: > >> You haven't given us enough information about what you are doing to >> provide >> you with a useful answer. In terms of size, 75K users is not really >> significant for AD from a size perspective. I wouldn't worry about that. >> >> Migration of users may be tricky, depending a great deal on how you have >> stored the users' passwords in SQL and whether your intent is for your >> users >> to have the same password they had before. >> >> Joe K. >> >> -- >> Joe Kaplan-MS MVP Directory Services Programming >> Co-author of "The .NET Developer's Guide to Directory Services >> Programming" >> http://www.directoryprogramming.net >> -- >> "Chris" <Chris@discussions.microsoft.com> wrote in message >> news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... >> > Hi All, >> > >> > I have question about Active Directory. We have developed a site it has >> > 75K >> > users on SQL server 2005 associated with roles, now we are thinking to >> > change >> > it to Active directory is it good idea or bad idea? if it is good how >> > to >> > migrate it. >> > >> > Thanks in advance. >> > >> > Chris >> >> >>
I'd suggest reading the patterns and practices guidance documentation on
using the ASP.NET membership provider framework. There is a ton written on this topic and you'll get better information by reading the existing documentation than by asking such a broad question on the newsgroups. The newsgroups are much better for asking specific technical questions. Google will find the P&P docs very easily for you. Since your passwords are stored in plain text, it should not be difficult to provision matching users in AD. You'll just need some sort of script to do it. You don't need Exchange unless you want to use Exchange to provision the AD users with mailboxes or use Exchange for some other email routing feature. Joe K. -- Joe Kaplan-MS MVP Directory Services Programming Co-author of "The .NET Developer's Guide to Directory Services Programming" http://www.directoryprogramming.net -- [quoted text, click to view] "Chris" <Chris@discussions.microsoft.com> wrote in message news:0F8FF162-0328-4B29-8271-8C5B25DCDF9B@microsoft.com... > > We are using username as firtsname.lastname password as plaintext. could > you please provide me more information on using the SQL and AD membership > providers for the integration with web application, how to implement it. > > aslo we want to use this AD for MOSS 2007, my question is do I need to > have > exchanger server for this to implementation, we are using this for > government > site. > > > Regards, > Chris > > > > > > "Joe Kaplan" wrote: > >> Can you provide more details on how the passwords are stored in the SQL >> database? If they are in plaintext or encrypted in a reversible format, >> then you should be able to recover them and use them provision identities >> in >> AD or ADAM such that the users will have the same username and password >> they >> used in SQL. >> >> However, if they are in some sort of 1 way hash format, then it might be >> very difficult to recover the plain text. That would make provisioning >> in >> AD very difficult. >> >> Username format might be a bit of a problem as well, depending the >> formats >> you allow in SQL. You would want those to be compatible with AD. ADAM >> gives you a little more flexibility here. >> >> I definitely recommend that you try to use the SQL and AD membership >> providers for the integration with your web application. They provide a >> nice abstraction layer over the user store that makes it easier for your >> application to not have to care where the users are stored. If you >> aren't >> using the membership providers now, I recommend that as your first step. >> >> Joe K. >> >> -- >> Joe Kaplan-MS MVP Directory Services Programming >> Co-author of "The .NET Developer's Guide to Directory Services >> Programming" >> http://www.directoryprogramming.net >> -- >> "Chris" <Chris@discussions.microsoft.com> wrote in message >> news:FBDD0F3B-CA1F-4658-893F-6B760047043E@microsoft.com... >> > Joe , >> > >> > Thanks for quick respone. >> > >> > We developed a site with public and privatre applications, for private >> > applications user need to login those users paswwords we dont want to >> > distrub, you are rite we want to use same passwords. >> > >> > Any kind of possible other solutions also welcome( there is no time >> > constraint for development). >> > >> > Regards, >> > Chris >> > >> > "Joe Kaplan" wrote: >> > >> >> You haven't given us enough information about what you are doing to >> >> provide >> >> you with a useful answer. In terms of size, 75K users is not really >> >> significant for AD from a size perspective. I wouldn't worry about >> >> that. >> >> >> >> Migration of users may be tricky, depending a great deal on how you >> >> have >> >> stored the users' passwords in SQL and whether your intent is for your >> >> users >> >> to have the same password they had before. >> >> >> >> Joe K. >> >> >> >> -- >> >> Joe Kaplan-MS MVP Directory Services Programming >> >> Co-author of "The .NET Developer's Guide to Directory Services >> >> Programming" >> >> http://www.directoryprogramming.net >> >> -- >> >> "Chris" <Chris@discussions.microsoft.com> wrote in message >> >> news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... >> >> > Hi All, >> >> > >> >> > I have question about Active Directory. We have developed a site it >> >> > has >> >> > 75K >> >> > users on SQL server 2005 associated with roles, now we are thinking >> >> > to >> >> > change >> >> > it to Active directory is it good idea or bad idea? if it is good >> >> > how >> >> > to >> >> > migrate it. >> >> > >> >> > Thanks in advance. >> >> > >> >> > Chris >> >> >> >> >> >> >> >> >>
[quoted text, click to view]
On Nov 30, 5:08 pm, Chris <Ch...@discussions.microsoft.com> wrote: > We are using username as firtsname.lastname password as plaintext. could > you please provide me more information on using the SQL and AD membership > providers for the integration with web application, how to implement it. > > aslo we want to use this AD for MOSS 2007, my question is do I need to have > exchanger server for this to implementation, we are using this for government > site. > > Regards, > Chris > > > > "Joe Kaplan" wrote: > > Can you provide more details on how the passwords are stored in the SQL > > database? If they are in plaintext or encrypted in a reversible format, > > then you should be able to recover them and use them provision identities in > > AD or ADAM such that the users will have the same username and password they > > used in SQL. > > > However, if they are in some sort of 1 way hash format, then it might be > > very difficult to recover the plain text. That would make provisioning in > > AD very difficult. > > > Username format might be a bit of a problem as well, depending the formats > > you allow in SQL. You would want those to be compatible with AD. ADAM > > gives you a little more flexibility here. > > > I definitely recommend that you try to use the SQL and AD membership > > providers for the integration with your web application. They provide a > > nice abstraction layer over the user store that makes it easier for your > > application to not have to care where the users are stored. If you aren't > > using the membership providers now, I recommend that as your first step. > > > Joe K. > > > -- > > Joe Kaplan-MS MVP Directory Services Programming > > Co-author of "The .NET Developer's Guide to Directory Services Programming" > >http://www.directoryprogramming.net > > -- > > "Chris" <Ch...@discussions.microsoft.com> wrote in message > >news:FBDD0F3B-CA1F-4658-893F-6B760047043E@microsoft.com... > > > Joe , > > > > Thanks for quick respone. > > > > We developed a site with public and privatre applications, for private > > > applications user need to login those users paswwords we dont want to > > > distrub, you are rite we want to use same passwords. > > > > Any kind of possible other solutions also welcome( there is no time > > > constraint for development). > > > > Regards, > > > Chris > > > > "Joe Kaplan" wrote: > > > >> You haven't given us enough information about what you are doing to > > >> provide > > >> you with a useful answer. In terms of size, 75K users is not really > > >> significant for AD from a size perspective. I wouldn't worry about that. > > > >> Migration of users may be tricky, depending a great deal on how you have > > >> stored the users' passwords in SQL and whether your intent is for your > > >> users > > >> to have the same password they had before. > > > >> Joe K. > > > >> -- > > >> Joe Kaplan-MS MVP Directory Services Programming > > >> Co-author of "The .NET Developer's Guide to Directory Services > > >> Programming" > > >>http://www.directoryprogramming.net > > >> -- > > >> "Chris" <Ch...@discussions.microsoft.com> wrote in message > > >>news:0620E3BC-F4D3-4A6C-A4B6-ADC27F591D37@microsoft.com... > > >> > Hi All, > > > >> > I have question about Active Directory. We have developed a site it has > > >> > 75K > > >> > users on SQL server 2005 associated with roles, now we are thinking to > > >> > change > > >> > it to Active directory is it good idea or bad idea? if it is good how > > >> > to > > >> > migrate it. > > > >> > Thanks in advance. > > > >> > Chris- Hide quoted text - > > - Show quoted text - Chris, from what was written above I see no clear case to migrate to AD. If you need it for integration with MOSS only, then I'm not sure if AD will be the best way in that case. SharePoint imports users from AD to the own SQL database, and it means AD will be as an intermediate-level "database" there. Moreover, SharePoint can obtain users connecting with AspNetSqlMembershipProvider to either the local or remote
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |