This page describes The Java interface is org.clazzes.util.sec.DomainPasswordLoginService from https://svn.clazzes.org/svn/util/trunk/clazzes-util/src/main/java/org/clazzes/util/sec/DomainPasswordLoginService.java

DomainPasswordLoginService Implementations

Current implementations

The following implementations are available:

• org.clazzes.login.ldap, 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.http, supporting a HTTP based API and therefore allowing for custom adapters to any backend there is
• org.clazzes.login.broker, 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.

Maven and Subversion repository

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

• If not out of scope: org.clazzes.login.openid (like provided by Wordpress, Google, Facebook, ...) 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.

DomainPasswordLoginService backend SDS

We are currently in the process of implementing a backend.

For now see http://svn.clazzes.org/svn/sds/trunk/ (SVN) and SDS (JIRA).