LS2 Authentication & Permission Development

From LimeSurvey Manual

Revision as of 16:53, 22 April 2009 by Anonymous (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Internal Authentication


On login a user is authenticated against different authentication mechanism - these authententication mechanisms can be set in his profile - the default authenticaction mechanism for a user is the LS internal one (username/password has stored in the users table) but it can also be set for example to only auth against LDAP. If a user manages to authenticate against one of the allowed mechanisms he/she may log in.

If a user athenticates the first time against a non-DB authentication mechanism his user is created automatically in the internal DB.

  • A non-DB authentication mechanism should be handled like a plugin and should be stored in the /plugins dir. Authentication mechanism plugin names have to start with the letters 'am' (for example: question types have qt)
  • There should be a table where a new authentication mechanism is registered and so made usable to the application
  • There should be a table which indicates wich user may use which authentication mechanism on login
  • The authentication plugin should have a GUI which is able to be shown in the general settings - as a separate tab for each authentication mechanism - the settings dialogue has to be adjusted to load and show the tabs from the authentication plugins automatically.

Permission - What areas does a user have access to?

LS2 is using CakePHP ACL to determine who gets access to what part of the application.

Please read up on CAKE ACL


  • Rights can be assigned to groups and users
  • Alias naming convention for ARO groups:  <groupname> model:group
  • Alias naming convention for ARO users:   user::<User ID> model:user


  • Naming convention for ACO application function groups (define areas of the application):  a<application area>
  • Naming convention for ACO application single function (define a certain function of the application):  s<function name>

User Security Groups

Restrictions are posed by ACL (see above)

  • Security Groups (can) have a single parent

Basic groups defined when installing the application:

  • Admins:

+Complete system access using a super-admin right

  • Users:

+Can login (if the 'canlogin' field in the users table is set to true), can take assigned surveys.

  • Custom groups:

+ACL allows to create new groups with custom rights.

Permission GUI

There has to be a GUI created to explicetly change permissions of a security group or create/delete these.

Permission areas

The application has to be logically separated into permission areas, optionally with fine-grained read/write/... permissions.

Permission & Authentication

Some authenticaction mechanism also provide permission data. In a first step this should not be considered