Roadmap
Plans for future releases
1.0
Not maintained anymore.
1.1
Currently active development: New features will still be added.
(see changes in 1.1.x).
1.2
-
Run as WSGI application.
Implement multi-threaded FastCGI and SCGI support based on
flup.
-
Support for proxied authorization (see RFC 4370).
-
Reimplement logging in a thread-safe and consistent manner for all run modes with module
logging.
-
Reimplement certificate/CRL viewer based on
pyasn1 to get rid
of Pisces license.
-
SSL support for stand-alone mode with support for CRL checking
and client certificates based on
M2Crypto
2.x
Planned as complete rewrite especially regarding HTML generation
and input form handling:
-
Will require upcoming
Python 3.1.
-
Automatic installation based on
setuptools.
-
Rewrite of user interface with a template-based web framework
following MVC design principle.
-
Handling of Get Effective Rights extension (multiple
solutions from various LDAP server vendors).
-
Support for simple paging control and server-side sorting.
-
More powerful handling of attribute input fields:
-
Multi-select fields for multiple attribute values.
-
Multiple check boxes for setting bits in an Integer.
-
Attribute values composed of multiple accompanying input fields.
-
Multi-line input fields for attributes
X-ORDERED set.
-
More flexible HTTP server integration (WSGI, FastCGI, SCGI) with other web framework.
-
User interface in multiple languages, better localization.
-
Support for language tags and ranges when displaying LDAP entries via
HTML templates.
-
Redesign of plug-in API:
-
Plug-in classes for pre-input, post-input actions at entry level
which makes it possible to implement attribute actions which depend
on other entry data (e.g. autogeneration/composition of attribute values).
-
Plug-in classes will be limited to a certain scope
by configuration (e.g. by matching LDAP URL).
-
User interface for constructing search filters with explicitly
given matching rules (support for matching rule use).
-
Support for forwardable tickets passed through SPNEGO and used with SASL/GSSAPI bind.
-
HTML-based help system.
-
Thread-pooling HTTP server instead of a new thread for each HTTP hit.
-
Run as service under Windows if needed (and configured).