Disable Password Reset Property

[Alberto Megía, geändert vor 11 Jahren.]

Good morning, my name is Alberto and this is the very first time I write here... so hi!
I have been looking for a property to disable Password reset when a new user login for the first time... but I did not find it.
What I have find was this:

https://github.com/liferay/liferay-portal/blob/master/portal-service/src/com/liferay/portal/kernel/util/PropsKeys.java

With the constant:

passwords.default.policy.change.required

But I did not work for me...

¿Any suggestions?
I know that you can disable it from Control Panel but I would like to know if there is a property to do that.

Thanks a lot!
Alberto

[Nicolas Hrbt, geändert vor 11 Jahren.]

hi
try company.security.send.password.reset.link and company.security.send.password

I've seen that the display of the link in the login page is conditionned to those boolean by looking at the navigation.jsp file.

++

[Apoorva Prakash, geändert vor 11 Jahren.]

Hi Alberto,

Yes it works...

But if you modified settings form control panel (that goes in database), then the setting of property files are overridden.

Try using a new database, Hopefully it will work.

Thanks and Regards,
Apoorva Prakash

[Alberto Megía, geändert vor 11 Jahren.]

First of all, thx to both of you for your quick responses!!!

Apoorva Prakash, I do not understand you. Supose the following:

I have LR Portal installed.
I want to change that property in portal-ext.properties by:

passwords.default.policy.change.required=false

Do I need to drop my DB and create it again? :S

[Nicolas Hrbt, geändert vor 11 Jahren.]

I gess that what he meant is that db take precedence over configuration file. Just test if it works, if i doesnt you may need to revert somehow the changes you made in the db.

[Alberto Megía, geändert vor 11 Jahren.]

OK!

But I did not do any changes... It is default password policy what I want to edit so ...

Do you know what tables manage that? I will try to figure out if I have no other choice

[Manish Kumar Jaiswal, geändert vor 11 Jahren.]

Try going to Control panel and then password policy and click on the default password policy and uncheck the Change Required Checkbox.

Regards
Manish

[Apoorva Prakash, geändert vor 11 Jahren.]

Nicolas Hrbt:

I gess that what he meant is that db take precedence over configuration file. Just test if it works, if i doesnt you may need to revert somehow the changes you made in the db.

Yes, you are righty right mate...
Thanks...

[Apoorva Prakash, geändert vor 11 Jahren.]

Alberto Megía:

First of all, thx to both of you for your quick responses!!!

Apoorva Prakash, I do not understand you. Supose the following:

I have LR Portal installed.
I want to change that property in portal-ext.properties by:

passwords.default.policy.change.required=false

Do I need to drop my DB and create it again? :S

Basically if you change any settings in Control Panel, that goes in database, and while you are trying to revert that value, its not reverted but updated with the modified value (might be blank or unchecked) into the database. And always database is given priority over property files. So this might be the reason.
try pointing to a new database once, for testing reason only.

Hope this will help.

Thanks and Regards,
Apoorva Prakash

[katakam praveen, geändert vor 9 Jahren.]

with out change the new database how it will work?

[katakam praveen, geändert vor 9 Jahren.]

HI,

I use this properties in portal-ext.properties


passwords.default.policy.change.required=false


but it is not working for me.

If i change from control panel for every user need to unchecked password policy.

please help me any one for this issue?

[Olaf Kock, geändert vor 9 Jahren.]

There are two things to keep apart: The default password policy can state that users need to change their password on first login. This will be applied when a new user account is created, or the password is changed by an admin. In this moment, the user will get a flag that they need to update their password on next login.

So, if you're talking about user accounts that have already been created, you'll have to take care of different data than when you want to change the default for all user accounts created in the future.

Never ever will you hear from me to use SQL to update your database, because once you get the hang of it, you'll use this for other purposes where it's not safe. If you only want to change 4 user accounts, it's best to edit them manually on Control Panel. If you have hundreds, thousands or more users, you should use the API: Create a script that modifies all user accounts (to remove the 'need to update password' flag) and saves them again.

To make sure that you don't have to do this again for future user accounts, change the default password policy. Do this on Control Panel (or at least validate there that the configuration is active). If you've already changed the default password policy through the UI, portal-ext.properties will be overruled by these settings.

[Alberto Megía, geändert vor 11 Jahren.]

Thanks a lot all of you for your responses and patience.

At the end,

passwords.default.policy.change.required=false

worked , so thx to all again.

Regards,
Alberto

[Alberto Megía, geändert vor 11 Jahren.]

Alberto Megía:

Thanks a lot all of you for your responses and patience.

At the end,

passwords.default.policy.change.required=false

worked , so thx to all again.

Regards,
Alberto

If anyone changes it in Control Panel, there is a table (PASSWORDPOLICY) that I can manage...

Thx again!

[Onochie Ojekwe, geändert vor 9 Jahren.]

Very on point.... been killing myself over the configuration files..... PASSWORDPOLICY is it! change CHANGEREQUIRED table field to FALSE!!

Very usefull.. Thanks guys!

[Olaf Kock, geändert vor 9 Jahren.]

Don't change the value in the database. There's a UI in Control Panel: Use that.

When you have a portal-ext.properties setting that doesn't work, the odds are that it's a value that can be overridden through the UI as well. If there's a conflict between portal-ext.properties and the values configured through the UI, the UI wins. While these values will be stored in the database, you must not change them manually. Rather use the UI or the API to change them again.

[Enrique Valdes Lacasa, geändert vor 8 Jahren.]

Thanks for the explanation Olaf. I would like to understand something at this point. Imagine that we have a brand new Liferay instance, and we hadn't manually changed any portal setting through the Control Panel UI yet. Then, would the properties:

passwords.default.policy.changeable=...
passwords.default.policy.change.required=...

work on true or false every single time, as long as we don't manually change them through the Control Panel UI?

Thanks!

[Olaf Kock, geändert vor 8 Jahren.]

(sorry for the late answer)

I believe you're right: If you've never started Liferay and the setting never made it into the database, it would be active. At least that would be my expectation. With this setting, I've never tried it out. And I somewhat expect that the default password policy is also written to the database quite early - either before the server got up the first time (with the values from portal.properties), or when you first edit and save it on the UI. I'll leave this for you to test.

[Madhava Venganapalli, geändert vor 9 Jahren.]

Hi Alberto,
Please add bellow entries in portal-ext.properties . Then it will work fine.

passwords.default.policy.change.required
users.reminder.queries.enabled=false
users.reminder.queries.custom.question.enabled=false

Regards,
Madhava Venganapalli

[darren rose, geändert vor 9 Jahren.]

Madhava Venganapalli:

Hi Alberto,
Please add bellow entries in portal-ext.properties . Then it will work fine.

passwords.default.policy.change.required
users.reminder.queries.enabled=false
users.reminder.queries.custom.question.enabled=false

Regards,
Madhava Venganapalli

you mean

passwords.default.policy.change.required=false