Hello everyone,
One of my colleagues has an error: "Error | Attachments renderer : invalid transaction id " every time he tries to open a new user request. He is an administrator as I am, and the error occurs only with his account.
Furthermore, when he tries to "mark as resolved" and user request the warning "this have been already updated" compare.
The error logs only say "Error | Attachments renderer : invalid transaction id | IssueLog "
He always has problems that no one else in our organisation have, like " Error | UI.php 'apply_stimulus' : invalid transaction_id ! data: user='user log in', class='UserRequest' | IssueLog".
Any ideas how should I deal with this problems? Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First, though I don't know about bug fixed matching this behavior, you should update to a more recent version. We will ship the 2.7.6 version soon, that could be a great idea to use it instead !
See the changelog : https://www.itophub.io/wiki/page?id=2_7_0%3Arelease%3Achange_log
To explain more : transaction_id are anti-CSRF tokens generated by iTop. Two implementations are available out of the box, and can be chose with the transaction_storage parameter. The default value is File, which means tokens are persisted to the file system.
The Session implementation may cause some issues when using memcached for example : this was the previous default implementation but was changed in iTop 2.5.2 / 2.6.0 after some bug feedbacks.
Actually when I first answered I was suspecting you were using the Session implementation, and the server was using for example cookies to maintain session, and you colleague browser wasn't playing nice with those.
Are you running on Windows ? If so when having the File impl you're getting transaction_id values that are file names, for example adm237E.tmp. You colleague may use an AV that filters such values ? Or use a proxy that process http response and transform those values ??
To understand the exact cause you would need to check the file generated on disk compared to the transaction_id hidden field value recieved in your colleague's browser.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone,
One of my colleagues has an error: "Error | Attachments renderer : invalid transaction id " every time he tries to open a new user request. He is an administrator as I am, and the error occurs only with his account.
Furthermore, when he tries to "mark as resolved" and user request the warning "this have been already updated" compare.
The error logs only say "Error | Attachments renderer : invalid transaction id | IssueLog "
He always has problems that no one else in our organisation have, like " Error | UI.php 'apply_stimulus' : invalid transaction_id ! data: user='user log in', class='UserRequest' | IssueLog".
Any ideas how should I deal with this problems? Thanks
Hello,
What iTop version are you running ?
Do you have the
transaction_storageconfig parameter set ?iTop verison 2.7.0-1
No i don't have the parameter transaction_storage in the config-itop.php., how should that be configured?
Thanks
Adding the parameter 'transaction_storage'='Session' to the config solved the problem!
Hi Madalina, do you fix the error adding this parameter ? In my config this paramener does'nt exists.
Hello,
First, though I don't know about bug fixed matching this behavior, you should update to a more recent version. We will ship the 2.7.6 version soon, that could be a great idea to use it instead !
See the changelog : https://www.itophub.io/wiki/page?id=2_7_0%3Arelease%3Achange_log
To explain more : transaction_id are anti-CSRF tokens generated by iTop. Two implementations are available out of the box, and can be chose with the transaction_storage parameter. The default value is File, which means tokens are persisted to the file system.
The Session implementation may cause some issues when using memcached for example : this was the previous default implementation but was changed in iTop 2.5.2 / 2.6.0 after some bug feedbacks.
Actually when I first answered I was suspecting you were using the Session implementation, and the server was using for example cookies to maintain session, and you colleague browser wasn't playing nice with those.
Are you running on Windows ? If so when having the File impl you're getting transaction_id values that are file names, for example
adm237E.tmp. You colleague may use an AV that filters such values ? Or use a proxy that process http response and transform those values ??To understand the exact cause you would need to check the file generated on disk compared to the transaction_id hidden field value recieved in your colleague's browser.