you would need to edit the super admin password stored wa_setings table to the SHA1 string.
you would need to edit the admin_cms/users_login.php, add the following code at line 1 to convert the password that is entered to an SHA1 string for login:
<?php
if(isset($_POST["Password"])){
$_POST["Password"] = sha1($_POST["Password"]);
}
?>
similar code would need to be added to the admin_cms/users_insert.php pages as well so that new users that are created will have the password stored in SHA1 format. the password form element on that page is named "password" so the code above would need to be altered slightly.
and code would need to be added to the users_update.php page to compare the submitted password with the one stored in the database to see if it is being changed and if so, convert the new password to the SHA1 format.
If you need assistance making this change, we can help you in a premiere support appointment.
Thank you for the assistance.
Just out of curiosity, the Security Assist tutorials were excellent in showing how to do encryption on passwords. So, it's obvious WebAssist understands how to do that.
Why would you do anything less in powercms?
And why would you not include a user name field when so many people are conditioned to expect one? I get a lot of phone calls from clients because they confuse the email field of the login screen with a user name field.