Hello, I’m migrating a forum to Discourse. I’m using the same approach as the discourse-migratepassword plugin to allow users to log in with their current password, but these passwords may be insecure. I want to allow the users to log in but force them to change their password after login if doesn’t comply with Discourse’s password settings. Is there a way to currently do this? If not, where I should look at to implement this as a plugin? Thanks!

Discourse now supports the native ability to expire passwords. To do so you will need to run: user = User.find_by_username(username) UserPasswordExpirer.expire_user_password(user) This can be done either by Discourse staff for hosted customers or by entering your container, running a rails console and executing this on the particular users.

Sounds like it would be useful as an option on the discourse-migratepassword plugin. Slightly surprised it isn’t already.

Yeah, we can use that in the plugin too, happy to contribute that back if I implement it. I was thinking in adding a custom_field to the user and render an alert until the user changes their password, but forcing them to change it sounds like a better option (not sure where to look to achieve this)

Well, I’m not forcing users to change their password, but we are rendering an alert on every login until they do so. [image] I’m setting a user.custom_fields['migratepassword_policy'] = true if the password doesn’t comply with Discourse settings and using that to conditionally render the modal, and we also send a password reset email once after they log in for the first time (with the insecure password) What do you guys think?

I think it was enabled without an option in the past - if your password was too short, you were required to do a password reset instead. The policy was flipped because this was locking people out of their accounts (dead email accounts).

Yeah, in this case we allow users to get into the platform with their current password, but we will render that modal until they change it (they can click OK or click outside the modal and it will close) Maybe adding a “contact support if you don’t have access to your email anymore” message will do in case of dead email accounts

hey exaktly the same we also need, we will create users via api and a default password… after user loged in first time, he should change his pass… how did you do that? Thx!

Instead of creating a user with a default password you should create the user with a random password and never send it to them. Then they can use the forgot password link on the login page to reset their password first before logging in.

99% our users have no mail address ^^ and we dont want do add so much mails only for “pass forget mails” is there no other way instead using real mails?

That will be a big problem as email is considered identity in Discourse…

If you want to have complete control over the login process in order to comply with your standard, I recommend using Official Single-Sign-On for Discourse (sso).

Erzwinge Passwortänderung nach dem Login

Produktunterstützung

Falco (Falco) 9. Dezember 2020 um 17:47 11

Wenn Sie den vollständigen Kontroll über den Anmeldevorgang haben möchten, um Ihre Standards einzuhalten, empfehle ich die Verwendung von Offizielles Single-Sign-On für Discourse (sso).

Thema		Antworten	Aufrufe
Migrated password hashes support Plugin	34	12957	2. Juni 2026
Cannot login to dev instance with imported user Development	5	1641	7. Februar 2018
Reset password with custom ruby file Development	9	1020	27. September 2023
Drupal password migrate into Discourse with discourse-migrate-password plugin Migration	4	894	15. Februar 2024
So I can't login anymore :( and won't receive email logins or forgotten password emails Product Support	9	2033	1. September 2019

Erzwinge Passwortänderung nach dem Login

Verwandte Themen