Very strange issue appears if we open Cockpit UI while no instances are created.
If we go to 389 Directory Server, we see Database management UI and it blocks the adility to create a new instance.

Maybe the PR is dependent on another PR here, and it is just a temporary bug.
I think we can merge the PRs and fix the issues on the way. Main part of the code here looks good to me.

Might be taking a totally different approach to password policy in 1.4.0 - this is now on hold and might be discarded...

Actually, this PR is still valid. The major password policy changes I previously mentioned are not going to make it into 1.4.0, but hopefully 1.4.1 instead. So this still needs to be reviewed...

Mark, does this depend on PR#49836 to be functional?

Mark, does this depend on PR#49836 to be functional?

Yes :-)

Ok, I could't apply this on top of 49836 because of merge conflicts.

Ok, I could't apply this on top of 49836 because of merge conflicts.

I'm not surprised - all my patches overlap, so they constantly have to be rebased :-( This is the problem when the these patches lay around, but development continues in other areas. Anyway I'm not complaining about you, it's just a nagging problem with developing UI features. I'll get it rebased right away!

This should be working in the UI global policy, but local password policies are not working in the UI yet - because dsconf doesn't have that functionality yet (WIP).

@vashirov - this patch should apply cleanly now...

It is possible to set the attributes in Global password policy.
LGTM. Ack

It is possible to set the attributes in Global password policy.

Yes that has been working for a while now, and the new attributes should also be working

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/2898

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.