RTC 3.0 : How to trace in syslog or in logs authorization errors
In order to meet security requirements for a customer who is using RTC 3.0 we need to trace authentification errors and authorizations errors in logs in order to collect them in a security log analyser named Qradar.
We managed to trace the authentification errors (wrong password for example) but we did not managed to trace the autorization errors (not authorized to deliver code for exemple, not authorized to access the workitem). Is there a way to trace theses errors in logs ? example of log we want to trace : Problem You don't have permission to Save Build Definition [server]. Reason
|
One answer
Out of the box there is not a solution for this. These messages are logged only to the client as "advisory" messages. The RTC API does not write these to any server side logs. Maybe, you could extend your server to write these errors to your own custom log.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.