## 1.0

Not maintained anymore.

## 1.1

In maintenance mode:

- No new features anymore.
- Important fixes will be provided.

## 1.2

Planned as small rewrite within 2013:

- Make use of HTML 5 features like <datalist> etc.
- CSS style chooser.
- Time zone chooser.
- More password hashing/crypting schemes.
- Support for simple paging control and server-side sorting.
- Run as WSGI application.
- Support for proxied authorization (see RFC 4370) based on successful authentication at the web server.
- 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
- Thread-pooling HTTP server instead of a new thread for each HTTP hit.
- Automatic installation based on setuptools.
- 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.
- User interface for constructing search filters with explicitly given matching rules (support for matching rule use).
- Run as service under Windows if needed (and configured).

## 2.x

Planned as complete rewrite in rather far future especially regarding HTML generation and input form handling:

- Will be based on Python 3.2.
- 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).
- 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).
- Support for forwardable tickets passed through SPNEGO and used with SASL/GSSAPI bind.
- HTML-based help system.