| email this FAQ to a colleague
Q: I've written a custom application for user administration on an LDAP membership
directory. Everything seems to work fine, but I've run into a problem with the
administrator account. When the admininistator tries to log in on my application, I get a
property not found when I attempt to get the admin's guid. I wrote an error
trap to catch it, create a GUID, and send it back to the Admininistartor's browser, but
that enerates an internal Site Server error. Has anyone seen this problem before or have any type of workaround? A: This is a known issue that the Administrator account (cn=Administrator,ou=Members,o=) is created without a GUID. Unfortunately, once the Member object has been created, you cannot update the GUID property so your attempted workaround (as you've seen) won't work. For now it would be best to trap the error because the only time you should see it is with the cn=Administrator object -- since all of your other users that you create via the MMC, the Migration Util. or programmatically will *not* be created unless you supply a GUID. - Dina Berry |
