You are right, the policy has now been updated since the last time I reviewed it. That said:
- Before, all manufacturers had the same password policy, which allowed us to ahave the same password policy.
- Manufacturers are now implementing their own policy, which means that each manufacturer may set different policies breaking a generalized approach.
That said, since this hardware seems to be non-certified, my recommendation is to change back to the default password policy and not the stricter one since it is not supported for this hardware. Adding support requires:
- Creation of the new password policy based on the previously created
- Testing across this new hardware and other hardware to ensure no regressions
As such, I've changed the title of this bug as a enablement request.
To work around the issue, revert back to the fdefault password policy instead of the stricter, as MAAS doesn't support the stricter password policy in this hardware.
Marton,
You are right, the policy has now been updated since the last time I reviewed it. That said:
- Before, all manufacturers had the same password policy, which allowed us to ahave the same password policy.
- Manufacturers are now implementing their own policy, which means that each manufacturer may set different policies breaking a generalized approach.
That said, since this hardware seems to be non-certified, my recommendation is to change back to the default password policy and not the stricter one since it is not supported for this hardware. Adding support requires:
- Creation of the new password policy based on the previously created
- Testing across this new hardware and other hardware to ensure no regressions
As such, I've changed the title of this bug as a enablement request.
To work around the issue, revert back to the fdefault password policy instead of the stricter, as MAAS doesn't support the stricter password policy in this hardware.