This as it allows users to choose passwords they feel they can memorize which decreases the chance they will write them down which is a sure way that it could easily be stolen. Took inspiration from your answer and updated the code.
A maximum password length never makes sense unless the system is storing them in plain text in which case you need to address that before you do anything [email protected] Thank you for pointing out the error after carefully reading the question even I reached the same conclusion.
Extending the Script Changing the colors is a great visual identifier for the user, but for added security, the script could be extended to disable the form submit button or alert the user before they submit the form if the passwords do not match.
The script and form could also be changed to use images for the confirmation rather than text.
This will compare the values in the two fields everytime a key is released in the confirmation field.
Note Front Page Server Extensions are a set of programs that provide access to special Front Page features, such as database processing, form processing, hit counters, and other built-in Front Page components that require server-side processing.
You can provide custom validation for your forms in two ways: server-side validation and client-side validation.
It consists of this process: This example contains the logic to validate a clear text password for a user against the password stored in the Profiles System.
The clear text password could, for example, come from a text box on a Web page. The second parameter is the clear text password for the user.
This example shows how to create a new function, called that you use to validate a password for a user in the Profiles System.