So, I haven't really got this fixed/explained, but I did get two responses that I appreciate that illuminated other areas for me. >>>>> Your ldap setup is configured incorrectly. You either have o=foo.bar.edu or you have dc=foo,dc=bar,dc=edu. You shouldn't have both. Right now what you have is the top level org tree is called int.crowncollege.edu with subcomponents that flow down from that called int, crowncollege, and edu. The correct synatx therefore would be: "ldapsearch -b "o=int.crowncollege.edu dc=int,dc=crowncollege, dc=edu" -s sub "uid=*"" You'd have to specify both the toplevel org and the subsequent subcomponents. I'd suggest you reinit your LDAP tree without the o (it's deprecated anyway) and use subcomponent naming schema for the base DN. >>>>> On this one, I realize that I shouldn't have it that way. However, after running the config-iscli tool, the o= section was added. I ran the search the way specified, however, it returns no results. comm_admin does return results for the same area though. >>>>> Derek Diget had a few things to check such as using Schema 2 and specifying the correct Base DN. I did those. He had these two good side notes as well. They've come in pretty handy. One thing to do is invoke the installer with the "-saveState" switch. This creates an state file of your settings and then you can actually do an unattended install using this file. Also, see ims.balius.com for a user site dedicated to Sun messaging server. It also has a link to the Info-iMS user mailing list. -- Thanks, -Aaron Taylor On 5/11/05, Aaron Taylor <kusoneko@gmail.com> wrote: > I've got the Directory, Identity, Administration, Messaging and Web > servers all installed and working from JES 2004Q2 on my workstation so > I can test them before deploying them. I ran into a problem with the > users now. > > When I run "commadmin user search" the output for a sample user is like this: > ########## > ########## > dn: uid=ataylor,ou=People,o=int.crowncollege.edu,dc=int,dc=crowncollege,dc=edu > sn: Taylor > maildeliveryoption: mailbox > cn: Aaron Taylor > objectclass: userpresenceprofile > objectclass: top > objectclass: iplanet-am-managed-person > objectclass: iplanet-am-user-service > objectclass: inetadmin > objectclass: organizationalperson > objectclass: person > objectclass: inetuser > objectclass: inetlocalmailrecipient > objectclass: iplanetpreferences > objectclass: ipuser > objectclass: inetorgperson > objectclass: inetsubscriber > objectclass: inetmailuser > nswmextendeduserprefs: meColorSet=0 > nswmextendeduserprefs: meTrashFolder=Trash > nswmextendeduserprefs: meDraftFolder=Drafts > nswmextendeduserprefs: meDateFormat=0/ > nswmextendeduserprefs: meSentFolder=Sent > nswmextendeduserprefs: meInitialized=true > uid: ataylor > givenname: Aaron > mail: ataylor@int.crowncollege.edu > mailhost: ultra60.int.crowncollege.edu > paburi: ldap://ultra60.int.crowncollege.edu:389/ou=ataylor,ou=People,o=int.crown > mailuserstatus: active > inetuserstatus: Active > ########## > ########## > > Fair enough. I'm not sure where in the install the > o=int.crowncollege.edu part came from. I wanted to use > ou=People,dc=int,dc=crowncollege,dc=edu for the users. Anyone have > thoughts on that one? > > So, a search of the whole repository spits this out as part of it's output: > ########## > ########## > bash-2.05# ldapsearch -b "" -s base "objectclass=*" > > objectClass=top > namingContexts=o=comms-config > namingContexts=o=PiServerDb > namingContexts=o=pab > namingContexts=dc=example, dc=com > namingContexts=dc=int,dc=crowncollege,dc=edu > namingContexts=o=NetscapeRoot > supportedExtension=2.16.840.1.113730.3.5.7 > supportedExtension=2.16.840.1.113730.3.5.8 > <snip> > ########## > ########## > > Again, fair enough. However, the next results have me confused. Both > of these commands return no results. However, they don't spit out an > error meaning that the specified BaseDN does exist. > > ########## > ########## > bash-2.05# ldapsearch -b "dc=int,dc=crowncollege,dc=edu" -s sub "o=*" > bash-2.05# ldapsearch -b > "ou=People,o=int.crowncollege.edu,dc=int,dc=crowncollege,dc=edu" -s > sub "uid=*" > ########## > ########## > > When I run "ldapsearch -b "dc=example, dc=com" -s sub "uid=*"" it > spits out all the sample users put in place so I can't seem to find a > syntax error on my part. Does anyone know how I can do an ldapsearch > and find the data created for the user ataylor that is shown in > commadmin? I would really appreciate it. > > Oh, also, the user ataylor is fully functional. I can use it to log > into the messaging server. > > -- > Thanks, > -Aaron Taylor _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed May 18 16:36:59 2005
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:47 EST