directory-fortress mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Haynes <>
Subject Re: Fortress and Openldap
Date Tue, 02 Aug 2016 19:47:44 GMT
Hi Shawn. I do have Fortress running with ApacheDS, but I also wanted to get it running with
OpenLDAP since we have more experience with that. I will take a look at those directions.
On a different note, is there verbose documentation for the Fortress REST API, such as using
Swagger or something like that? At the moment, I am looking at the test cases to find the
payload examples and file to see the method URI.

      From: Shawn McKinney <>
 Sent: Tuesday, August 2, 2016 2:58 PM
 Subject: Re: Fortress and Openldap
A google search found a few resources describing a conversion of slapd.conf to OLC.  I don’t
know how credible they are, but it might be worth a try, after you get it working with the
conf file.


> On Aug 2, 2016, at 1:48 PM, Shawn McKinney <> wrote:
>> On Aug 2, 2016, at 1:30 PM, Ted Haynes <> wrote:
>> Hi Shawn. No, I did not see that. With the newer version of OpenLDAP, the slapd.conf
file is deprecated. Now it expects ldif file to be imported instead of using a schema file.
Do you have any suggestions? I have seen in some examples the use of ldif files and ldapadd
> Ted, my guess is slapd.conf will continue to be supported for some time, i.e. many years. 
I haven’t tested fortress with the cn=config utility so can’t provide the instructions. 
There are many other settings besides schema that must be applied so my recommendation is
learn fortress/openldap with the .conf file first before attempting to use the online config
- if that is a requirement for you.
> You can submit a ticket to fortress JIRA and we’ll try to work it in, although I can’t
make any promises of how soon.  If you are feeling adventurous, and want to try implementing
using the online config, we’ll do our best to support you, and incorporate what you learned
in the doc.  But again, learn using the conf file first, before making the leap to the other.
> Thanks,
> Shawn  

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message