It is more an implementation of an authentication and autorization scheme which works on the database level.
We have a stored procedure that authenticates users and supplies them a time bombed access token which has to be supplied to stored procedures that return, change or add data.
That implements access checking in the database layer, as many conditions apply where users are not allowed to change some records, but are allowed to change other.
For user data I was able to implement this, but the problem is the password changing. I already had to break some part of the functionality by bypassing the stored procedure and creating a view to be used as users table, but the very point is that the password in that view is not the password of the user but data related to the access token.
To change the password I have to use a stored procedure which verifies the old password (SHA2-256 hashed) and is supplied the access token in addition and also does certain checks on the new password.
Usually I would do this using the before password change event - if it worked like the before login event where I could transform the password to a value that is then compared to the password value from the view.
If it was an option to access the auth table directly I would do this. But unfortunately it is not.
I understand from your reply that there is no sufficient way to do this within the functionality PHPRunner provides and that if that functionality is needed I have to change the exported PHP files. Please let me know if that is not correct.