Project

General

Profile

Bug #801

Underdark Login Framework relies on fixed fieldnames

Added by Niek Bergman over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
PageMaker
Target version:
Start date:
2012-05-03
Due date:
% Done:

0%

Estimated time:

Description

The ULF login handler expects a "username" and "password" field in the login form for it to do its job. These names could be more generic, and should ideally be developer-configurable.


Related issues

Related to µWeb - Bug #814: Underdark Login Framework - User creation and removal, password changesNew2012-05-11

History

#1 Updated by Jan Klopper over 7 years ago

Is this using /underdark/web/static/js/login.js?

If so, this is not true, as that code relies on an init function to hand it a dict of jquery IDs:

InitLoginFields({user:'#secure_user',
                 pass:'#secure_pass'});

Maybe want to make the code aware of string ID's, css queries, and direct objects being handen to it, to avoid the need for jquery

#2 Updated by Niek Bergman over 7 years ago

Jan: the LoginMixin still expects a 'username' and 'password' field in the POST.
E.g.:

    password = str(self.post.getfirst('password', ''))

Also, the database field the LoginMixin looks at in SQL is named 'name'.

#3 Updated by Elmer de Looff over 7 years ago

  • Subject changed from ULF Login has predefined "username" and "password" fields. to Underdark Login Framework relies on fixed fieldnames
  • Description updated (diff)
  • Category set to PageMaker
  • Target version set to µWeb beta release

Also available in: Atom PDF