summaryrefslogtreecommitdiff
path: root/source4/setup/pwsettings
AgeCommit message (Collapse)AuthorFilesLines
2009-09-30s4:pwsettings - Improve error handling and introduce "choice" typeMatthias Dieter Wallnöfer1-13/+10
- Improve the error handling according to Jelmer's suggestions - Print out the error messages on "stderr" - Add also here the "choice" type for arguments
2009-09-21s4:scripts - Reintroduce "-H" parameterMatthias Dieter Wallnöfer1-2/+7
I removed it since on some scripts it was present, on others not - so I thought it wouldn't be really needed. This was a bad decision (pointed out by abartlet). So I reintroduce it on all scripts (to have consistent parameters).
2009-09-18s4:scripts - Cleans also the rest under the "setup" directory upMatthias Dieter Wallnöfer1-17/+22
- I removed also the "-H" parameter since those scripts are all thought for the use on a local s4 domain controller. Another reason is also the bind as SYSTEM account which itself is only possible on local binds.
2009-09-18s4:domainlevel/pwsettings - Remove unused importMatthias Dieter Wallnöfer1-1/+0
2009-09-18s4:pwsettings - Simplify the error handling a bitMatthias Dieter Wallnöfer1-5/+2
2009-09-10s4:pwsettings: Show default values in help messages.Andrew Kroeger1-4/+4
2009-09-10s4:pwsettings: Add 'default' option for password complexity.Andrew Kroeger1-2/+2
2009-09-10s4:pwsettings: Added validation.Andrew Kroeger1-4/+26
Validate that each field is within its allowed range. Also validate that the maximum password age is greater than the minimum password length (if the maximum password age is set). I could not find these values documented anywhere in the WSPP docs. I used the values shown in the W2K8 GPMC, as it appears that the GPMC actuaally performs the validation of values.
2009-09-10s4:pwsettings: Don't assume a value for pwdProperties.Andrew Kroeger1-2/+2
If we cannot retrieve the value, do not assume a particular value. The fact that we could not retrieve the value indicates a larger problem that we don't want to make worse bypossibly clearing bit fields in the pwdProperties attribute.
2009-09-10s4:pwsettings: Run all updates as a single modify() operation.Andrew Kroeger1-31/+19
This ensures that all changes are made, or none are made. It also makes it possible to do validation as we go and abort in case of an error, while always leaving things in a consistent state.
2009-09-10s4:pwsettings: Added --quiet option.Andrew Kroeger1-16/+17
Also changed all non-error status output to use the message() function, which respects the --quiet option.
2009-09-07s4:pwsettings: Correct off by factor of 10 for ticks.Andrew Kroeger1-4/+4
The tick conversion math was off by a factor of 10 due to the incorrect usage of the "e" notation. The expression "XeY" means "X * (10^Y)", so the correct expression is 1e7 to get the correct adjustment for ticks.
2009-09-06s4:pwsettings - Introduce the LDB modify flags in the right wayMatthias Dieter Wallnöfer1-27/+8
We can't emulate them through the LDB changetype flags since they haven't the same constants! The previous behaviour led to huge problems.
2009-08-17s4:python tools - Centralise the lookups for the default domain (root) in ↵Matthias Dieter Wallnöfer1-8/+4
the call "domain_dn" from SamDB
2009-08-11s4:pwsettings script - Fix a small glitchMatthias Dieter Wallnöfer1-5/+10
This fixes the problem with the setting and getting of the "minPwdAge" and "maxPwdAge" attributes. I wanted to handle them in days but forgot to add conversions (from "ticks" (tenth of microsecond) -> "days" and backwards).
2009-08-07s4: Add a new script for setting password properties for a domain in a ↵Matthias Dieter Wallnöfer1-0/+202
easier way