1.0|
0.16.x|
0.15.x|
0.14.x|
0.13.x|
0.12.x|
0.11.x|
0.10.x|
0.9.x|
0.8.x|
0.7.x|
Ancient|
Overview
Release Date: 2008-09-23
-
The basic searchform is displayed now when the server to connect
to is chosen from the select list of [Connect] page. This avoids
the annoying message "no search results found" when
connecting without specifying a base DN.
-
Corrected HTML templates for object class organization.
-
Values for form parameter search_attrs can now be 1000 chars long.
Release Date: 2008-09-06
-
Fix in schema viewer: When doing a wildcard search schema elements
with several NAMEs are not listed more than once anymore.
-
New plugin module eduperson and HTML templates for
eduPerson.
-
Exception ldap.NO_SUCH_OBJECT is ignored when adding a new entry
and therefore reading the parent entry (for determining the governing structure rule).
This happens when adding the root entry in a naming context.
-
Documentation update:
Update to python-ldap 2.3.5+
is required if the LDAP server's subschema contains name forms.
-
Fixed a regression when adding a new entry if the structural object class of the superior
entry cannot be determined (e.g. a rootDSE without objectClass attribute).
Release Date: 2008-09-04
-
Fixed more regressions in case the subschema subentry
cannot be read (e.g. because of access control).
-
Fixed a regression when trying to modify the rootDSE...
Release Date: 2008-09-03
-
Fixed regression in SubSchema.get_applicable_name_form_objs()
which raised an exception when trying to add a new entry (choosing [New Entry])
in root naming context (empty DN).
-
Fixed regression when generating context menu in schema viewer in case
the subschema subentry cannot be read (e.g. because of access control).
Release Date: 2008-09-03
-
It is now possible to specify a set of named templates for basic search forms
with parameter searchform_template
which appear in the context menu when displaying a search form.
-
When renaming an entry the new superior DN can be searched. The possible
candidates are then displayed als select list. Also see new
host-/backend-specific parameter
rename_supsearchurl
which is a named set of LDAP URLs to specify how to search for a new superior DN.
-
Support for DIT structures rules and nameforms:
-
When adding a new entry the DIT structures rules applicable to the parent entry
are used to determine the set of possible structural object classes
for the new entry when displaying the object class select form.
-
Possible name forms are displayed as RDN template strings in the [Rename]
input form if there are any defined for the structural object class of the entry.
-
When renaming an entry the filter for searching the new superior DN
is suggested according to the governing structure rule for the entry to be
renamed.
-
Improvements to plugin modules/classes:
-
Placeholders can now be appended at the end of the DN portion of
DynamicValueSelectList.ldap_url and are substituted by
entry's current DN, entry's parent or the best matching naming context.
-
New plugin module dhcp for
draft-ietf-dhc-ldap-schema.
-
Improvements in schema browser:
-
A certain type of schema elements can be selected in the context menu.
-
Simple wildcard search is supported on OIDs and NAMEs
with asterisk (*) being placed at the begin and/or end of the search string.
-
Better error handling in the schema viewer when displaying a matching
rule in case an attribute type is referenced in an attribute type
description as SUP which is not present in the subschema.
-
Adding another attribute value in the entry input form for a textual attribute
is now done with an additional submit button [+] which results in an
additional input field being displayed for the chosen attribute type.
The advantage is that the additional input field is generated by an
accompanying plugin class if possible.
-
The monitor page can now be restricted by source IP. See new parameter
access_allowed
in the monitor configuration module.
-
In the monitor page the number of all web sessions initialized since
start up is displayed.
-
A warning message is displayed (instead of exception being raised)
if the user did not choose a STRUCTURAL object class when adding a new entry.
-
Small improvements in cert/CRL viewer:
-
If the subject- or issuer DN of a cert/CRL contains characters not valid
for the given ASN.1 string type the viewer now falls back to
display the invalid characters in hex-escaped form (instead of raising
UnicodeError).
-
The OIDs of attribute types used in subject and issuer names are displayed.