...
The following implementations are available:
- org.clazzes.login.httpldap, supporting LDAP backends like ADS
- org.clazzes.login.jaas, using container provided JAAS authentication
- org.clazzes.login.sql, using any legacy SQL database, i.e. one managed by SDS (SQL Directory Service)
- org.clazzes.login.ldaphttp, supporting a HTTP based API and therefore allowing for custom adapters to any backend there is
- org.clazzes.login.sqlbroker, providing access to all other login services available in the OSGi container, selecting the mechanism by the request's authentication domain
For testing them there is a testpad webapp using org.clazzes.login.adapter.http, see there.
...
All implementations have the new maven groupId
, org.clazzes.login
, and a new svn repository: https://svn.clazzes.org/svn/login.
Ideas for future implementations
...
Authentication against external Authentication Providers
- OAuth2/OpenID Connect client: org.clazzes.login.openid (like provided by Wordpressoauth (authenticate against github, Google, Facebookmicrosoft cloud services,...) or Mozilla's upcoming counterpart.
OSGi wrapper HttpLoginServiceAdapter and Testpad
The OSGi side for the new login serivce approach consists of one small bundle, org.clazzes.login.adapter.http, that listens for providers of the DomainPasswordLoginService
interface and exports them adapted as HttpLoginService.
Token OTP Provider
For adding two-factor authentication support, the module org.clazzes.login.yubikey is provided, which has been
DomainPasswordLoginService backend SDS
...