Relationship Graph
View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007864 | mantisbt | authentication | public | 2007-03-29 09:47 | 2011-08-05 02:45 |
Reporter | dlmueller | Assigned To | dregad | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Summary | 0007864: Native support for SHA1 authentification within Mantis | ||||
Description | Since several years we use the python based Wiki-Clone "MoinMoin" (http://moinmoin.wikiwikiweb.de) as the central knowledge management system. We have about 50 user account. To ease user help desk ("I forgot my password") we allow the users to reset their password like Mantis does. The passwords are stored encrypted. The same usernames and passwords are also used within our HTTP-Authentification within the Apache Webserver. For all users we've choosen the same username within MoinMoin and within Mantis. Since both systems have their own user management changing the password within one system does not affect the password in the other system. Therefore we'd like to sync the encrypted passwords between both systems. Since the passwords within MoinMoin and Apache .htaccess are SHA1 encrypted it we cannot use them directly within Mantis. Therefore it would be nice, Mantis would also support SHA1 authentification. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I'd like to generate an encoded password that is compatible to the output of the program ''htpasswd''. See the following example: Within PHP one can reproduce this output by using To ensure complete compability one must prepend the prefix "{SHA}" before the output of the base64 encoded SHA1 hashed password. I will implement this authentification method and provide a patch. The following function will be used: |
|
With the leading prefix "{SHA}" the SHA1 encrypted passwords need 34 bytes and thus exceed the current size of the field "username" which is defined as "VARCHAR(32)". To be compliant to the output of "htpasswd" I would prefer an according change of the DB-scheme i.e. change the field "password" in "mantis_user_table" from currently "varchar(32)" to say "varchar(40)" or "varchar(64)". Until then: |
|
sha1("mypassword", true) is not correct for php4 I've copying the phpldapadmin function, and that now work well with php4 in core/authentication_api.php : // $t_processed_password .= base64_encode( sha1( $p_password, TRUE ) ); # @@@ added by dlmueller, see issue 0007864 for details ^M
Thanks for your works. |
|