Message Boards

Issue in Password Policies - After DB Migration

Prabakar Duraisamy, modified 3 Years ago.

Issue in Password Policies - After DB Migration

New Member Posts: 11 Join Date: 1/27/20 Recent Posts
Hello,
We are working on Liferay Migration from version 6.1 to 7.1.3.
Our server environment is Wildfly11.
After database migration, when we click Password Reset Policy, We are getting "Password Policies is temporarily unavailable." Refer Attachment
when i searched, i get the following link.
https://issues.liferay.com/browse/LPS-99845
Is it an existing defect which is in unresolved status? Can you please clarify?
Regards
Prabakar
thumbnail
Alberto Chaparro Terleira, modified 3 Years ago.

RE: Issue in Password Policies - After DB Migration

Liferay Master Posts: 549 Join Date: 4/25/11 Recent Posts
Hey Prabakar,
This issue seems related to the permissions associated to the model com.liferay.portal.kernel.model.PasswordPolice. Please take a look at the log when access to the page, maybe you can try a workaround removing the problemaitc entries or creating the proper permissions.
I hope it helps.

Boris Doris, modified 3 Years ago.

RE: Issue in Password Policies - After DB Migration

New Member Posts: 4 Join Date: 12/28/20 Recent Posts

Hi Prabakar.

Did you resolve this problem? How you did it?

I have same problem

Marco Danieli, modified 2 Years ago.

RE: Issue in Password Policies - After DB Migration

New Member Posts: 6 Join Date: 3/29/22 Recent Posts

I know this question is quite old, but I didn't find any solution of the problem in liferay forum yet.

I had same problem after DB migration, so I tried to find a workaround to this problem.

Making some tests on our test environment I saw that I was able to create new Password Policy, without seeing these in password policies page. These policies were saved in DB in the password policy table (passwordpolicy) and liferay saved also resource permission in the appropriate table in DB (resourcepermission). Watching resource permission table I saw that new password policies had different types of data in primkey and primkeyid respect of Default Password Policy. So I replaced default password policy values of columns primkey and primkeyid in resourcepermission table with passwordpolicyid of default password policy in passwordpolicy table.

After this replacement, I don't see anymore the problem and I see the password policies in page (maybe you have also to delete DB cache from configuration panel to see changes)

It can be a valid solution or it's too dirty?

Are there more clean solutions?