New authentication server for the legacy Wifidog protocol

Registered by pierrelux on 2010-03-22

The new authentication server must be kept small and should not implement features that are already provided by some proof-tested components. A plugin architecture must be the main point of focus.

A first basic authentication plugin should be made available soon so that communities could then derive custom plugins for their own needs.

The authentication server must support the legacy Wifidog protocol as well as the new protocol (being drafted).

http://www.symfony-project.org/ will be used. DB abstraction is an important aspect so that AuthPuppy could be deployed with any hosting company, hence the choice of PHP.

CMS will not be part of AuthPuppy, as this will instead be delegated to systems such as Wordpress, or Drupal.

Blueprint information

Status:
Started
Approver:
gbastien
Priority:
Essential
Drafter:
None
Direction:
Approved
Assignee:
Philippe April
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Beta Available
Milestone target:
milestone icon 0.1.0-alpha
Started by
gbastien on 2010-03-22

Related branches

Sprints

Whiteboard

Basic core feature implementation:

[papril] node addition/edition
[papril] gateway-auth server communication (ping, auth) v1 protocol
 * basic splash-only login for users
[gbastien] admin login : FINISHED, installed symfony plugin sfDoctrineGuardPlugin to manager administrative users and groups

Put in place and document the following:

 * multilingual support
[gbastien] easy plugin architecture : IN ALPHA STAGE
[gbastien] access rights for eventual granularity of access provided by plugins: TO BE TESTED AND DOCUMENTED sfDoctrineGuardPlugin will be used

Basic plugins

[gbastien] User authentification with signon: PLUGIN, SEE plugin_signon_auth blueprint for more info
 * Mac address authentication
 * Web service (for Wordpress plugin and such): see plugin-web-service blueprint
 * Node group management (recursion in the nodes)
 * Statistics: see plugin-statistics blueprint

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.