I can not build the server...

Module not found: Error: Can't resolve './server.jsx'

I can not build the server...
Module not found: Error: Can't resolve './server.jsx'

Sorry, missed the "git add", fixed now...

Fields for LDAP Port and LDAPS Port accept any character. Can we make it num only?

In Server Settings - Advanced - If I click on Server Read-Only, it doesn't make Save button active.

In Server Settings - Disk Monitoring - I think the fields Disk Monitoring Threshold, Disk Monitoring Grace Period and Server Logs are aligned in an odd way. Maybe, we can put it more to the left (so it's the same level with Enable Disk Space Monitoring? I understand why it is done like this but it really looks off to me...
Attaching a screenshot to the issue.

In Tuning & Limits advanced settings - Enable Normalized DN Cache box has a text field beside it. If we zoom the page just a bit (or user will have a smaller screen to begin with - for me it was broken to begin with), then the field goes to the next line and it looks broken.
Attaching a screenshot to the issue.

In Logging rotation policies, can you please add num limits for Hour and Minute?

Fields for LDAP Port and LDAPS Port accept any character. Can we make it num only?

Yup, I missed that.

In Server Settings - Advanced - If I click on Server Read-Only, it doesn't make Save button active.
In Server Settings - Disk Monitoring - I think the fields Disk Monitoring Threshold, Disk Monitoring Grace Period and Server Logs are aligned in an odd way. Maybe, we can put it more to the left (so it's the same level with Enable Disk Space Monitoring? I understand why it is done like this but it really looks off to me...
Attaching a screenshot to the issue.
In Tuning & Limits advanced settings - Enable Normalized DN Cache box has a text field beside it. If we zoom the page just a bit (or user will have a smaller screen to begin with - for me it was broken to begin with), then the field goes to the next line and it looks broken.
Attaching a screenshot to the issue.
In Logging rotation policies, can you please add num limits for Hour and Minute?

These are already number inputs with min and max limits

Changes applied, please review...

I know that you just moved the code but could you please check the Security tab too?

Server Secure Port can be a number also.

And a few checkboxes on the bottom are off in Security Configuration tab (attaching a screenshot)

Require Secure Connections
Verify Certificate Subject Hostname
Allow Weak Ciphers

I am not sure if it was like this before your PR...

The rest looks good as far as I can see.

I know that you just moved the code but could you please check the Security tab too?
Server Secure Port can be a number also.
And a few checkboxes on the bottom are off in Security Configuration tab (attaching a screenshot)
Require Secure Connections
Verify Certificate Subject Hostname
Allow Weak Ciphers

I'll look into this. Did you also check the password policy stuff that got moved to the database tab? Just checking :-)

I'll look into this. Did you also check the password policy stuff that got moved to the database tab? Just checking :-)

Yeah-yeah, it looks good! Interesting solution with 3 tabs for local pwpolicy managment.

I'll look into this. Did you also check the password policy stuff that got moved to the database tab? Just checking :-)

Yeah-yeah, it looks good! Interesting solution with 3 tabs for local pwpolicy management.

I kind of stole the idea from you and what you did with the replication monitor :-) It's tough when a modal is too small for what you need, but I think it works well enough.

All changes made, and added nsTLSAllowClientRenegotiation to the security page. Please review...

LGTM! Ack

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/3946

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.