directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Commented] (DIR-320) ACL/ACI documentation section missing, filled with TODOs.
Date Tue, 10 Nov 2015 23:25:11 GMT


Emmanuel Lecharny commented on DIR-320:

Hi Julia,

glad you finally were able to setup a LDAP server that fits your need.

ATM, I would say that ApacheDS is probably the right tool when you want to develop an application
in Java that requires an LDAP server, just because ApacheDS is an embeddable LDAP server.
I do agree that the documentation is lacking, and this is a pity.

I'm sorry that you weren't able to find the information you wanted on our web site, and as
I said, we would have be glad to have some help, but I also understand that it's not something
you can provide, which is plain ok. We can just say that we are going to work harder and get
the missing parts added.

Have a nice trip with OpenLDAP, it's certainly not a bad choice !

> ACL/ACI documentation section missing, filled with TODOs.
> ---------------------------------------------------------
>                 Key: DIR-320
>                 URL:
>             Project: Directory
>          Issue Type: Improvement
>          Components: sitedocs
>            Reporter: Julia Smith
>            Assignee: Emmanuel Lecharny
> I had to scrounge around on the web to find content for the authorization sections. Your
current release's documentation's chapters are simply filled with "TODO" when it comes to
defining grants/denials, which is a problem for people evaluating studio for use and might
limit its adaptation.
> Here is the version of documentation that actually still presents content. It actually
works with the current version of studio.
> You  might consider incorporating it into the current release's documentation.
> Also there is little or no apparent online discussion of ACI with the exception of a
PDF of what looks like a PPT presentation.

This message was sent by Atlassian JIRA

View raw message