I want to put users into an instance of ADAM so that ADAM looks similar to a typical, real, Active Directory server.
I'm developing an application that integrates with LDAP. I've tested with OpenLDAP and its core.schema. Now I'd like to test with with Active Directory, but the closest I can get to that using my equipment is by testing with Microsoft ADAM.
I don't know exactly how to begin with ADAM. Zero experience with it and Active Directory. I'm guessing I need to import the MS-AdamSchemaW2K3.LDF because I see "sAMAccountName" in there, and I think I want that to be like Active Directory?
Added after reading a couple answers...
The answers so far aren't specific enough for what I'm looking for. I did get ADAM to work and my app can talk to it, but what I want to do is to have ADAM working the way a typical (if there is such a thing) Active Directory installation would work, same schema, authentication, even though I'm just using ADAM in a workgroup network, on Windows XP.
JumpCloud is a Better Alternative to Active Directory Users enjoy seamless access to their system (Windows, Mac, and Linux), local and remote servers (AWS, GCP etc.), LDAP and SAML based applications, physical and virtual file storage, and VPN and WiFi networks via RADIUS.
LDAP and RADIUS are the best active directory alternatives for Linux and Mac.
Active Directory Application Mode (ADAM) is a Lightweight Directory Access Protocol (LDAP)-compliant directory service used for building directory-enabled applications. ADAM is intended for users who do not want to set up a domain controller to enable directory services.
Active Directory (AD) is Microsoft's proprietary directory service. It runs on Windows Server and enables administrators to manage permissions and access to network resources. Active Directory stores data as objects. An object is a single element, such as a user, group, application or device such as a printer.
ADAM isn't really a complete replacement for Active Directory. For example, ADAM doesn't understand different group types, and doesn't include a RootDSE by default. You could test against ADAM but you may run into slight differences in your query structures.
If you are developing an application that will depend on Active Directory then you really should be building your application against an Active Directory. I have been able to get several Domain Controllers running just fine in Virtual PC (free) using only 300mb of memory and a free evaluation version of Windows Server.
If, however, you are building an application that simply needs an LDAP directory and isn't going to be using Active Directory than ADAM may work out just fine. The schema extension file you mentioned (MS-AdamSchemaW2K3.LDF) would work just fine but you would want to setup RootDSE for easier binds.
Lastly, Microsoft AD/AM isn't really Admin friendly, especially in terms of troubleshooting. I ended up writing an application to help troubleshoot AD/AM issues that you may find useful.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With