Romano Trampus

Found to set log_level_min to LogAPI::LEVEL_TRACE but no trace of notification come in log (or I'm looking at the wrong log, /var/www/html/log/error.log). I fond only: array ( '$sObjectClass' => 'Incident', '$sTransactionId' => '8239-0nd6Rg', '$sTempId' => '8239-0nd6Rg', '$aInlineImagesId' => array ( ), '$sUser' => '8239', 'HTTP_REFERER' => '(here is the url)', )

I'm tryng to create a Trigger (and an Action) to send an email to staff when a new request is inserted by a caller using the standard portal. The email test runs fine, but I'm unable to catch the event. There is any way to debug triggers, i.e. understand which events are fired when a new request is inserted?

Hi Pierre, I moved to a discussion, and probably it's still there :-) Thank you, romano On Tue, Feb 23, 2021 at 5:04 PM Pierre Goiffon pgoiffon@users.sourceforge.net wrote: Hello Romano, I've received an email with your answer but when opening this ticket your message is blank ?!?? In the email I received your were asking if it's ok to contribute and yes of course it is ! See the CONTRIBUTING.md files in our public repos. [tickets:#1939] https://sourceforge.net/p/itop/tickets/1939/ UserLDAP auto...

OK, I have more than 30.000 ldap users and it's a non sense to import all of them because probably only 5% will ever open a ticket for support. So I manged to implement auto creation of ldap users. The first attempt was to make a new external authentication extension. But I'm not familiar with PHP and I've not an IDE installed. So I managed on modifying some files. Probably not the best solution but it's functional, so..... Here are the files modified. I've tested on env-production but they must...

while I agree with you that is not a good idea to modify the core code, I think it's useless to duplicate code just for a variable in a function and few lines. The "problem" is that - as far as I can understand - the LDAP login (UserLDAP class) is "hardcoded" in the form login mode. Probably because a historical reason. It could be much more easy if the function public static function ProvisionUser in loginwebpage.class.inc.php can accept an extra parameter for the UserType that, at the moment, is...

hile I agree with you that is not a good idea to modify the core code, I think it's useless to duplicate code just for a variable in a function and few lines. The "problem" is that - as far as I can understand - the LDAP login (UserLDAP class) is "hardcoded" in the form login mode. Probably because a historical reason. It could be much more easy if the function public static function ProvisionUser in loginwebpage.class.inc.php can accept an extra parameter for the UserType that, at the moment, is...

Hi Pierre, (ok, let me know if it's better to move on a discussion) while I agree with you that is not a good idea to modify the core code, I think it's useless to duplicate code just for a variable in a function and few lines. The "problem" is that - as far as I can understand - the LDAP login (UserLDAP class) is "hardcoded" in the form login mode. Probably because a historical reason. It could be much more easy if the function public static function ProvisionUser in loginwebpage.class.inc.php can...