Ommitting the domain component

[padde]

I need to fake a LDAP configuration that uses no domain component dc=... at all. However, Ladle assumes that such a domain component always exists in several different places. Would it be possible to extend Ladle such that the domain component can be fully ommitted? Any help on this issue would be greatly appreciated. It would be great if you could make the domain component optional. Unfortunately I don't feel that I have the skill to create a PR on my own. Thanks for your time!

Here's an minimal example LDIF that I would like to be able to read with Ladle:

version: 1

dn: o=myorg
objectclass: organization
objectclass: top
o: myorg
l: Berlin
postalcode: 12345
streetaddress: 123 Some Street

dn: ou=myunit, o=myorg
objectclass: organizationalUnit
objectclass: top
ou: myunit

dn: uid=abcd123, ou=myunit, o=myorg
objectclass: organizationalPerson
objectclass: inetOrgPerson
objectclass: top
objectclass: person
cn: John Doe
sn: Doe
givenname: John
uid: abcd123
userpassword: {SHA}fDYHuOYbzxlE6ehQOmYPIfS28/E=

I have tried the following so far:

---

• Omit the domain option in Server.new

Produces the following error

ApacheDS process failed: FATAL: ERR_268 Cannot find a partition for o=myorg

---

• Set the domain option in Server.new to '' (empty string)

Produces the following error

ApacheDS process failed: FATAL: Missing argument for option: d

---

• Set the domain option in Server.new to 'o=myorg'

Produces the following error

The domain component must start with 'dc='.  'o=myorg' does not. (RuntimeError)

---

• Set the domain option in Server.new to 'o=myorg'
• Comment out the check for ds= in the Ladle source code
  https://github.com/NUBIC/ladle/blob/master/lib/ladle/server.rb#L105-L107

Produces the following error

ApacheDS: WARN: The Rdn 'o=myorg' is not present in the entry
ApacheDS process failed: FATAL: ERR_250_ENTRY_ALREADY_EXISTS o=myorg already exists!

---

• Set the domain option in Server.new to 'o=myorg'
• Comment out the check for ds= in the Ladle source code
  https://github.com/NUBIC/ladle/blob/master/lib/ladle/server.rb#L105-L107
• Omit the organization in the LDIF file completely

Curiously, this starts a LDAP server successfully, but still produces a Warning in ApacheDS:

ApacheDS: WARN: The Rdn 'o=myorg' is not present in the entry

Of course, now I have a running server but am missing the organization details.

[tpbowden]

@paddle Did you ever resolve this or just give up using the gem? (which looks abandoned anyway)

[padde]

@tpbowden didn't find a good solution with this gem, if I recall correctly. I am no longer working on the project where I used this so I am not sure how this is handled now.

[ghost]

@rsutphin Any progress on that issue?