|
first off, yeah, i'm probably doing it wrong. I'm using some schema in ways it wasn't designed to be used; more as a proof of concept ldap is something i'm trying to learn better for 2017, so i'm diving into crazy stuff. Here's what i've got: base is dc=CENSORED,dc=com. I created an OU called "prodhosts" which is a container for lists of servers under that there's cn=bedford and cn=dallas, both of which are "rooms" in schema. Under that are lists of servers, with an attribute "roomnumber" for the type of server they are (e.g web, or job) So, what i want to do is get a list of all servers under cn=bedford,ou=PRODhosts,DC=CENSORED,dc=com with attribute roomnumber=web: code:
|
#
?
Jan 26, 2017 17:37
|
|
|
|
| # ? Apr 25, 2024 16:42 |
|
|
Just shooting from the hip, but how is the room attrb defined? Some attributes can only hold certain types of values (string, int, ect). I seem to remember that this can also affect the matching algorithms used for that attribute. What's the schema that provides room number? And what are the object classes that make up your server object?
|
|
#
?
Jan 27, 2017 03:26
|
|
|
Another thought is that you could run it with debug and see what the command is passing the server.
|
|
#
?
Jan 27, 2017 03:46
|
|
|
ok, the debugmode hint gave me what i needed, but hell if I know why. The command line iwas using, it compltelty ignored my filterspec. I am using a much simpler one and it works: code:
|
|
#
?
Jan 27, 2017 05:02
|
|
|
Cool, glad you got it working. Only thing I can think of is that it interpreted ldap://lgldapdev100 as a filter and then defaulted to objectClass=*. Your original command would probably work if you put a -H in front of ldap://lgldapdev100.
|
|
#
?
Jan 27, 2017 07:28
|
|