Hello. We have installed and configured OTRS 3.3.8 on an Ubuntu 12.04.02 LTS, using Postgres 8.4 as database backend. Each time we try to create a new customer user we get this kind of error: ----------------------------------------------------------------- otrs ERROR: null value in column "pw" violates not-null constraint ----------------------------------------------------------------- I checked the column of the table customer_user and, indeed, the pw value must be not null. Following the suggestion found at this url: http://lists.otrs.org/pipermail/otrs/2010-November/033772.html I changed the Kernel/Config.pm file and declare the password field as mandatory. This changes the password attribute as I can see from the generated source page: ----------------------------------------------------------------- <label class="Mandatory" for="UserPassword"><span class="Marker">*</span> Password:</label> <div class="Field"><input type="password" id="UserPassword" name="UserPassword" class="W50pc Validate_Required " value="" maxlength="100" /> <div id="UserPasswordError" class="TooltipErrorMessage"><p>This field is required.</p></div> <div id="UserPasswordServerError" class="TooltipErrorMessage"><p>This field is required.</p></div> </div> <div class="Clear"></div> ----------------------------------------------------------------- But this trick doesn't resolve our problem because the password field is still missing in the insert statement as I can see in the database log: ----------------------------------------------------------------- ERROR: null value in column "pw" violates not-null constraint STATEMENT: INSERT INTO customer_user ( title, first_name, last_name, login, email, customer_id, phone, fax, mobile, street, zip, city, country, comments, valid_id, create_time, create_by, change_time, change_by) VALUES ( '', 'a', 'b', 'TESTNAME', 'dad@example.com', 'sd324', '', '', '', '', '', '', '', '', 1, '2014-09-24 10:42:01', 3, '2014-09-24 10:42:01', 3) ----------------------------------------------------------------- How can we fix this problem? Did I miss some steps of the previous solution? Could it help if I change the attribute of the pw column of the table allowing to insert empty password? Thank you in advance for any help you could give me. Best regards, Maila Fatticcioni