nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Querying AD

System

Has anyone written any code that will bind to AD and query the GC to get useful data by login id (e.g. email address, fullname, etc.). I have lots of places where I need to transform userids into human readable stuff (e.g. assignment pulldowns in workflow), where we are currently using mapping files. It seems a little foolish to maintain data in a file when it already lives in the directory. I've seen some example code on perl.com and other places, but it's been long enough (four years) since I played with LDAP that I'm not catching on as quickly as I should.

Find more posts tagged with

Comments

Dwayne

Well, it's not AD (directly), but this is a routine that I wrote for one of my clients to map the User ID to full name. You can extend it to get the various other tidbits.


my %DCs = ();
sub MapUIDToName {
        my $uid = shift;
        my $result = $uid;      # Default to the user ID
        my ($domain, $name) = $uid =~ m|(.*)\\(.+)|;

        if($domain && $name) {
                # See if we've already looked up this DC
                $domain = lc $domain;
                my $server = "";

                if(!defined($DCs{$domain})) {
                    my $rc = Win32API::Net::GetDCName("", $domain, $server);

                    # Discard any leading \\ that might be there
                    $server =~ s/\\\\//;
                    $DCs{$domain} = $server;
                } else {
                    $server = $DCs{$domain};
                }

                my %hash = ();

                $rc = Win32API::Net::UserGetInfo($server, $name, 10, \%hash);

                $result = $hash{'fullName'} || $uid;
        }

        return Unicode:tring::latin1($result);
}

Current project: TS 5.5.2/6.1 W2K

Migrateduser

I just figured out my major malfunction - I wasn't supplying a good filter. When I finish up the things I need to do to turn this from a test script to usable code, I'll post it.

Your example with the Win32API::Net module would solve 90% of my problem, but I think there are going to be times when I will need to know what OU they are in, or what there phone number is, or that sort of thing, that it doesn't look like it would give me (from my very quick read of the Win32API::Net perldoc)

Migrateduser

OK - here is a cleaned up version of my test script - I decided to cut and paste it into a module, the rest of which you don't care about. Obviously, to use in you environment, you'll have to replace mycorp.com and the user and pw (unless anonymous binds are allowed)

use strict;
use Net::LDAP;

# Connect and bind

my $ad = Net::LDAP->new("mycorp.com")
or die "Could not connect!";

my $msg = $ad->bind("user\@mycorp.com", password=>"yourpwhere");

my ($userid) = @ARGV;
my $base = 'DC=mycorp,DC=com';

# Filter on the staff membership and
# first letter of samaccountname attribute

my $filter = "(samaccountname=$userid)";

# Which attributes should be returned?

my $attrs = "samaccountname, mail";

# Execute the search

my $results = $ad->search(base=>$base,filter=>$filter,attrs=>$attrs);

# How many entries returned?
my $count = $results->count;
my $entry;
my $directory;

for (my $i=0; $i<$count; $i++) {

$entry = $results->entry($i);

print $entry->get_value('givenname')." ".
$entry->get_value('sn').
" (".$entry->get_value('mail').")".
"\n";

}

# Write the file

# Unbind from the server

$ad->unbind;