Manually reseting admin login details?

[Incog]

I setup Blesta the other day to take it for a test drive, and I seem to have misplaced (AKA, not saved) my admin details. I tried the password reset, though no email has arrived. Looking at the MySQL tables I see that there is a staff ID 1. which is me, and the email address associated with that ID is in fact correct. But still, not link sent to me.

What's the best way to do a reset of this manually?

[Paul]

21 hours ago, IncogHost said:

I setup Blesta the other day to take it for a test drive, and I seem to have misplaced (AKA, not saved) my admin details. I tried the password reset, though no email has arrived. Looking at the MySQL tables I see that there is a staff ID 1. which is me, and the email address associated with that ID is in fact correct. But still, not link sent to me.

What's the best way to do a reset of this manually?

Here's the steps to reset the admin password in order of simplest to most involved:

To reset the staff password visit /admin/login and click the "Reset My Password" link. Enter your username, and click the "Reset Password" button. You should get an email with a password reset link within a few minutes.

If you don't get an email, ensure that your username is correct. In phpMyAdmin or other MySQL database utility, look in the users table. Your username should appear in the "username" column, typically where id equals 1, as the primary staff account is the first user to be created.

If that still doesn't work, you will need to temporarily enable legacy passwords. Please see [encryption](http://docs.blesta.com/display/user/Configuration+Files#ConfigurationFiles-Encryption) in the user manual, specifically Blesta.auth_legacy_passwords and set it to true.

Then, in the users table for your username, update the password field to: 5f4dcc3b5aa765d61d8327deb882cf99

Then, try logging in with your username and the password password. Reset your password.

Then, change Blesta.auth_legacy_passwords back to false.
 

[Incog]

Thank you Paul, that certainly did the trick. I had to enable legacy passwords temporarily.