Last post Sep 03, 2008 01:03 PM by vidalsasoon
Sep 03, 2008 07:32 AM|mrthrifty|LINK
Hi, This is my first thread and I am not a "techie" so please be gentle!
I work for a company with a successful ASP solution. We do not currently offer LDAP or Active Directory compliance.
Our solution uses 3 factor login; Database name, user name, and user password.
Potential and existing customers are asking for LDAP and AD compliance and I am trying to justify the development internally so I can then sell the functionality.
Our solution is written using;
Any ideas on the time it would take a developer to factor in the coding and lookups, and what things should I say we need to consider?
Sep 03, 2008 08:36 AM|XIII|LINK
do you use the SqlMembershipProvider currently? If so you can easily plug in an LDAP provider for membership by configuring it in the web.config.
Sep 03, 2008 09:05 AM|mrthrifty|LINK
Before I ask internally, if we do use this, what sort of workload would you feel this would require for coding to allow Single Sign On from a customers domain.
My aim is to enable our users to login as they do using LDAP/AD, they will then gain access to our solution without the need to login again on our front page.
As mentioned, I am not too technical but would appreciate an idea of whether this would take, hours, a few days, or weeks, plus the obvious testing.
Sep 03, 2008 09:42 AM|XIII|LINK
do you have to use an LDAP that's already installed or not? In the former case you'll need to craft a custom provider that can read out the LDAP directory. I haven't used the default one that ships with ASP.NET myself but I'll bet that it involves some predefined
way of setting up your LDAP structure.
Sep 03, 2008 01:03 PM|vidalsasoon|LINK
If you're familiar with the authentication provider model, this link should help you:
Examples with AD, LDAP and SSO.
Once your web.config is set up, use the built in login controls and test it out. You shouldn't need a single line of code.