Flexible JDBC Realm – features

about

• index
• news

download

• software

documentation

• snapshot
  • features
  • installation
  • caching
  • management
• 1.3
  • features
  • installation
  • caching
  • management
• 1.2
  • features
  • installation
  • caching
  • management
• 1.1
  • features
  • installation
  • caching
• 0.5
  • features
  • installation
• 0.4
  • features
  • installation
• 0.3
  • features
  • installation
• 0.2
  • features
  • installation
• 0.1
  • features
  • installation

Table of contents

• Table of contents
• Features
• Next Release
• Future features

Features

• Support for any database model for managing users and groups.
• Storage of passwords as plain text or using any message digest as supported by Java's MessageDigest.getInstance(String) can be used.
• Configuration of the digest algorithm. Any digest algorithm supported by MessageDigest.getEncoding(String). Also, it is possible to avoid use of a digest algorithm alltogether. Also the character set used to convert the password to its byte array representation as input to the digest algorithm can be configured. The default character set is that returned by Charset.defaultCharset().name().
• Optional configuration of the encoding of the password digest. Hexadecimal and base64 encoding are supported. In addition, text encoding is supported whereby the byte array as output from the digest algorithm is converted back to a string using the character set. The default is hexadecimal encoding.
• Support for a seed in the encoding where the seed for a specific user is retrieved from the database. When a seed is used the password is encoded together with the user-specific seed to prevent dictionary attacks. The way the seed is used together with the password is configured using a format string.
• When Hex encoding is used, the hex output is always padded with leading zeroes. By default 32 characters are used but this can be configured to an arbitrary number.
• Logging: Use FINEST level logging to see details.
• Caching to minimize database access. By default, no caching is used to keep behavior identical to previous versions. A simple non-clustered expiry cache is provided with a configurable timeout and a JMX interface to manipulate the cache.
• Extendibility: It is possible to write your own cache and configure it through FlexibleJdbcRealm.
• Logging (FINEST level) when users are evicted from the cache.
• Performance statistics for database access and caching.

Next Release

-

Future features

This version of Flexible JDBC Realm is considered feature complete, but who knows?