Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This describes the design ideas for the next generation of the login service stuff.

Base interface DomainPasswordLoginService

The base interface only provides a login verification API, without any HTTP session handling.

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

Implementations

Current implementations

The following implementations are available:

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, and a new svn repository: https://svn.clazzes.org/svn/login.

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 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 a HttpLoginService.

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 (https://svn.clazzes.org/svn/gwt/trunk/gwt-*-login-service).

 

 

  • No labels