I'm not going to answer every question you posed, but Auth.pm should always allow the user/password that is stored in /etc/koha.conf to authenticate with full privileges (including the ability to create new accounts and set passwords through the members module). Steve. On Sun, 8 Dec 2002 acli@ada.dhs.org wrote:
In article <3DEF08D6.40107@free.fr> you write:
Ambrose Li a �crit:
Hi,
stupid question. Has anyone tried the latest CVS and noticed anything unusual? The intranet module seems to have stopped working; the home page is giving me a member login screen.
I don't know if it's me, or it's the Koha in CVS. Anyone can confirm this?
not a stupid question ! but i can't answer until monday/thuesday, because i'm in Dombes Abbey for my 1st koha install :-)
I think I can reproduce this... in 1.2.3RC23. I have filed Bug 147 in bugs.koha.org.
From a cursory glance of Auth.pm and Security.pm, it seems that user names are stored in uppercase and passwords are MD5-hashed, but I can't seem to be able create a valid user to log on to the
Does anyone know the structure of the users table (i.e., how are user names stored in the usercode field? how is the password stored? what is the meaning of the "level" field? and what is the relation between the "usercode" field and access to the intranet module)? librarian interface. Thanks very much!
-- Ambrose Li <a.c.li@ieee.org> http://ada.dhs.org/~acli/cmcc/ http://www.cccgt.org/
DRM is theft - We are the stakeholders
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel