Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.1
-
Fix Version/s: 3.1.0 Beta 3
-
Component/s: Core
-
Labels:None
Description
This issue contains several ideas around improving LDAP support in Jive Messenger. It is inspired by the following thread;
http://www.jivesoftware.org/forums/thread.jspa?threadID=14151
1) Use paged search controls when supported. This will increase performance and allow support for much larger sets of users. The following site has info on using the search control:
http://forum.java.sun.com/thread.jspa?threadID=578347&tstart=45
2) Add meta-data to LdapManager about supported features. When starting up, we should check the LDAP server to see what extensions it supports. This can be done with:
-----------
Here is a simple program for finding out the list of extensions that an LDAP server supports.
// Create the initial context
DirContext ctx = new InitialDirContext();
// Read supportedextension from the root DSE
Attributes attrs = ctx.getAttributes(
"ldap://localhost:389", new String[]{"supportedextension"});
Here is the output produced by running this program against an LDAP server.
{supportedextension=supportedextension:
1.3.6.1.4.1.1466.20037
}
---------------
A list of controls at: http://www.iana.org/assignments/ldap-parameters
and the paged results at: http://www.rfc-archive.org/getrfc.php?rfc=2696
3) Try to extract ldap server vendor information:
http://www.rfc-archive.org/getrfc.php?rfc=3045
4) Create an LDAP admin page in the admin console that displays LDAP info and allows some configuration changes. The new admin page should try to replace having to manually edit the wildfire.xml file. Moreover, the new page should let configure which groups are shared groups or let assume that all groups should appear in group members.
http://www.jivesoftware.org/community/thread.jspa?threadID=19270
Issue Links
| This issue is related to: | ||||
| OF-304 | Implement Paging For Searches |
|
|
|
5) Allow binaryData to be used from LDAP. Base64 encode it before output. This would allow vCard photos to be stored in LDAP in the jpegPhoto field.