[prev in list] [next in list] [prev in thread] [next in thread] 

List:       drupal-development
Subject:    [development] authentication module without the @foo
From:       gordon () heydon ! com ! au (Gordon Heydon)
Date:       2006-01-30 22:10:02
Message-ID: 1138659006.7402.41.camel () localhost ! localdomain
[Download RAW message or body]

Hi,

If this is a 4.7 development then take a look at logintoboggan as it
gets around this so that you can log in using your email address instead
of your user name.

Maybe you could do something similar.

Gordon.

On Mon, 2006-01-30 at 18:54 +0100, B?r Kessels wrote:
> Hi,
> 
> I recently developed mysql_auth module [1]. Its rather silly/small, but still 
> usefull. It allows users to authenticate against any other database, not 
> nessecarily in drupal form, postgre works too, despite the name.  I am 
> testing now, but will release as soon as I have this last issue solved :)
> 
> Right. What I want, is to get the authentication to be performed for any user. 
> Not just user@foo, but if Joe is not fond local, then it should check for Joe 
> in the other table. Drupal has this hardcoded, so the authentication hooks 
> cannot do this. 
> 
> But I was wondering if there is another way to authenticate users? Some 
> user_load trick I am not aware of? Ot maybe a patch that I can +1 to remove 
> the hardcoded @ check?
> 
> Bl?????r
> 
> [1] http://help.sympal.nl/user/help#mysql_auth
> 
> PS: I know about the way to share user tables but that is
>  a) only usefull for tables in the form of drupal tables. (you cannot check 
> for MyStrangeAPPusers)
>  b) not perfect, because you need to share a /lot/ of tables, also ones like 
> the {sequences}. it has side effects
>  c) not very safe if you want to allow users from A to log in on B but those 
> from B not on A.

[prev in list] [next in list] [prev in thread] [next in thread]