Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Verlinkung detailseiten pro bundle, Reorganisation


The Java interface is org.clazzes.util.sec.DomainPasswordLoginService from plan the following implmentations now


Current implementations

The following implementations are available:

We will create a new svn repository "login".

For testing:

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 groupIdorg.clazzes.login


Future ideas for implementations:, and a new svn repository:

Ideas for future implementations

  • org.clazzes.login.jdbc (Standalone using local Database)
  • 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 exists for the new login serivce approach consists of one small bundle, org.clazzes.login.adapter.http, that listens for providers of the DomainPasswordLoginService the DomainPasswordLoginService interface and exports them adapted as a HttpLoginService (see .

Deprecated/obsolete HttpLoginServices

Current org.clazzes.gwt.login.* LoginServices combining login API and HTTP session handling will become obsolete: gwt-jaas-login-service,gwt-ldap-login-service, gwt-http-login-service (*-login-service).

Package for the wrapper: org.clazzes.login.adapter.http

OSGi-bundle/project name: http-login-adapter

URL of exported DomainPasswordLoginServices: /http-login/<login.mechanism>/login