setpassword

Sets the password of the indicated record. The setpassword function works on the operator, guests and b_instr tables. The force parameter only ignores the ominpwage setting in prefs for an operator. The number of passwords that cannot be reused for an operator (oreusepswd) is always respected. If successful, setpassword re-writes the passwords field of the indicated record.

The password functions require a minimum password length of eight with at least one character and one number for each password. They enforce not reusing a certain number of passwords for operators as set with prefs.oreusepswd. They don’t allow passwords to be changed until a certain period of time has elapsed (again, for operators as set with prefs.ominpwage). They log the number of failed attempts (if prefs.ologattmpt and prefs.glogattmpt are set). They can lock out an operator for a period of time (minutes in prefs.olocktime) if prefs.ologattmpt is exceeded. And they can lock out a guest if prefs.glogattmpt is exceeded.

XML tag	Description
<table>	Table (the operator, guests or b_instr table).
<id>	The op_code for the operator table, the guest_no for the guests table or the instr_id for the b_instr table.
<password>	Password. Note: What is entered into the <password></password> tags for both checkpassword and setpassword is case sensitive. However, passwords entered in Sales or SysManager and hashed/stored in the SiriusSQL database for operators and instructors are always upper case. So when using these functions for operators and instructors, always enter characters in the <password></password> tags in upper case. Characters entered into the <password></password> tags for guests can be mixed case as these passwords are hashed/stored in the SiriusSQL database in mixed case.
<force>	Set to 1 to override lockouts.