Export reporting login Audit different than admin

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install business reporting 0.8.0.3
2. Enable audit in alfresco-global.properties
3. Enable Audit Export on moreFrequent harvesting and Execute 
FillReportingDatabase

What is the expected output? What do you see instead?
I've monitored the login audit table (reportingloginaudit) and I see that the 
rows's number reach 50.000 on about 200.000 audit entries.
In the scheduled moreFrequent harvesting the 50.000 rows will be recalculated 
each execution based on last date? (More precisely will be always the last 
50.000 row order in descending way?)

What version of the product are you using? On what operating system?
Alfresco 4.0e on Windows Server 2008

Please provide any additional information below.
Is possibile to define an audit filter to exclude login activities done from 
admin user?

Best Regards
Vincenzo

Original issue reported on code.google.com by vincenzo...@gmail.com on 24 Feb 2014 at 2:34

[GoogleCodeExporter]

Vincenzo,

Apologies, you are right... I see a hardcoded 50.000 value, and for some reason 
I did not implement the same mechanism as against ordinary noderefs. (Fetch say 
50.000, then the next 50.000, until done) This mechanism is the reason why it 
is ordered by 'latest'. I gues I have to revisit this implementation... This 
will be there in the next version. I hope you can stretch it until then...

You can edit the filter any way you like. I just provided a basic 
implementation of a filter. Feel free to create many more... (And exclude the 
one provided :-) )

(You wanna create an unmonitored backdoor?)

Original comment by tjarda.p...@incentro.com on 28 Feb 2014 at 9:01

• Changed state: Accepted

[GoogleCodeExporter]

Hi Tjarda,

Thanks for your answer,

Just for information I've add an audit filter that permit to avoid the
audit at least for admin user:

audit.filter.alfresco-api.post.AuthenticationService.default.enabled=true
audit.filter.alfresco-api.post.default.enabled=true
audit.filter.alfresco-api.post.AuthenticationService.authenticate.default.enable
d=true
audit.filter.alfresco-api.post.AuthenticationService.authenticate.args.enabled=t
rue

audit.filter.alfresco-api.post.AuthenticationService.authenticate.args.userName=
~System;~null;~admin;.*

This could be useful to add in your module (alfresco-global.properties)

A good feature that could be added is the compatibility with other DB as
well as PostgreSQL and Oracle

(You wanna create an unmonitored backdoor?) Sure, I can try to help you to add 
some functionality in your package.

Best Regards
Vincenzo

Original comment by vincenzo...@gmail.com on 28 Feb 2014 at 3:51

[GoogleCodeExporter]

Got my main issue in reporting fixed, this one is next...

Tjarda

Original comment by tjarda.p...@incentro.com on 3 Mar 2014 at 11:46

[GoogleCodeExporter]

And the bad news is that due to the nature of the callback mechanism by 
Alfresco I cannot determine how big my resultset is. In other words, it is hard 
to determine when (or how often) to repeat the query to get all results... 

I think this is a problem only in the initial loading of the reporting database 
though.... I updated the value of 50.000 into Integer.MAX_VALUE and I am going 
to sleep over it... 

Suggestions are welcome...

Original comment by tjarda.p...@incentro.com on 4 Mar 2014 at 10:21

[GoogleCodeExporter]

Original comment by tjarda.p...@incentro.com on 4 Mar 2014 at 10:22

• Changed state: Started

[GoogleCodeExporter]

Option as discussed in #4 is implemented in the next release. Hereby I will 
close the issue....

Original comment by tjarda.p...@incentro.com on 6 Apr 2014 at 8:56

• Changed state: Fixed