Re: Advice requested : Storing SID String in SQL table

I'm glad you like the book. Thanks a lot. I too like using SDS.Protocols.
It is a little geekier and requires a bit more code, but once you get some
nice wrappers going, it is pretty effective. In retrospect, it would have
been nicer to have more coverage on it in the book, but we had to finish it
sometime and it actually started before we ever saw 2.0, so it was hard to
backtrack.

If you are interested, I started a series of blog posting on my blog
(www.joekaplan.net) demonstrating a bunch of things that can't be done in
ADSI and require SDS.P (or native LDAP API).

My main issue with SDS.P is with Microsoft with some of their own APIs.
Stuff like CDOEXM for Exchange mailbox provisioning requires ADSI and makes
it hard to do this kind of thing in raw LDAP (IADsTSUserEx is another
example). Most of the Exchange programming story is pretty crappy though
(as you have probably already seen). :)

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
--
"Russell Mangel" <russell@xxxxxxxxx> wrote in message
news:Ofsbt75wGHA.4596@xxxxxxxxxxxxxxxxxxxxxxx

"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:%231cYWtmwGHA.1624@xxxxxxxxxxxxxxxxxxxxxxx

Another potential option to consider might be to store the user's AD GUID
(assuming you are talking about AD users and groups here). That fits
nicely into a normal SQL unique ID column and is always 16 bytes. You'd
then need to look up the SIDs if you need them from the directory.

Joe K.

Thanks, I also found this information in your
excellant book. (2006 Directory Services Programming).

FYI
I really like the System.DirectoryServices.Protocols
for LDAP access the best. I use LDAP access to get
as much information as I can for Exchange mailboxes,
before I use MAPI 1.0 for mailbox archiving.

Russell Mangel



.

Relevant Pages