Set "User cannot change password" flag automatically

kalbrecht

Hello there,

Within my osTicket Setup (1.18.1) i am having the issue that i do not want our users to be able to change their password.
They are currently authenticating against our Active Directory via LDAP Plugin (0.6.2), which makes this feature redundant.
As of now, i only see the option to manually set the "User cannot change password" flag on each User.
That is an issue, as

1. A User only exists to be edited after they have logged in or written an Email, making proactive changes impossible
2. We have alot of Users, making this untenable.

We could just allow this feature and ignore it, as resetting the password has no effect to User authentication using AD.
But it still might mislead Users and cause unnecesary support requests.
Is there any way to automate setting this flag upon User creation without editing the codebase?

Thanks alot,
Kevin

KevinTheJedi

kalbrecht

Nope, you will need to modify the codebase or setup a custom trigger/script in SQL.

Cheers.

kalbrecht

Unfortunate, but i really appreciate the fast reply.
I will set out to trigger this on user creation using SQL.

If you have any, could you provide some small help so i may find where to begin / where the necesary tables or option is located?

Otherwise, consider this thread closed.

Thanks alot,
Kevin

KevinTheJedi

kalbrecht

I don’t have anything of the sort; but we do have ERD’s available:

https://docs.osticket.com/en/latest/Developer%20Documentation/Database%20ERDs.html

Cheers.

kalbrecht

I have been tinkering a bit and (for anyone that is interested)

I tried to create a custom trigger within the table ost_user_account, which looks like this:

delimiter //
create trigger deny_usr_pw_reset AFTER INSERT ON ost_user_account FOR EACH ROW BEGIN UPDATE ost_user_account SET status = 9; END;//
delimiter ;

However, this causes the initial login to fail (with sometimes the error message to provide a valid phone number (we use 4 digit ones), although i have altered the Contact Form to not validate the user phone number.)

I have tried to delay the trigger with

DO WAIT(3)

,but that just makes a "Please wait" Prompt pop up for 3 seconds, resulting in a failure to create the user.
It appears the custom trigger is interrupting the normal order of operations for osTicket.

I will continue my search next week.