# Migrated password hashes support

**URL:** <https://meta.discourse.org/t/migrated-password-hashes-support/19512>\
**Category:** Plugin\
**Created:** [Setembro 1, 2014, 5:51pm UTC](https://meta.discourse.org/t/migrated-password-hashes-support/19512 "2014-09-01T17:51:25Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![pgr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pgr/32/156783_2.png) [@pgr](https://meta.discourse.org/u/pgr)\
**Post date:** [Agosto 10, 2018, 5:05pm UTC](https://meta.discourse.org/t/migrated-password-hashes-support/19512/17 "2018-08-10T17:05:30Z")

</div>

Hi. I am thankful for this plugin, it’s proving very useful for my Kunena4 migration.

But I ran into problems which were quite hard to understand - only after setting up an IDE and debugging through the code I was able to figure out why my logins weren’t being accepted.

The passwords I was trying were right, and the hashing was also working fine. The problem was with Discourse’s password requirements:

- I had to go in Admin / Settings / Plugins and check ` migratepassword allow insecure passwords`

- I had to go in the database and run `UPDATE email_tokens SET confirmed = TRUE` to bypass the email tokens mechanism (note that my approach was a bit brute force here - if you have existing users you’re not migrating, use a less aggressive approach)

The difficulty was especially with the first part, because I had no clue why the login was being rejected. I hope this helps someone.

And again, thanks for the plugin! 🙂

---

_[View the full topic](https://meta.discourse.org/t/migrated-password-hashes-support/19512)._