-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audit logging ignores multitenant mode #152
Comments
feel free to send in a PR.
|
Ok, looking at it... it seems that the AuditLogListener is only reacting to events from the DEFAULT data source. Whatever happens in other data sources related to different tenants is completely ignored. Could you point me in the right direction for fixing this? |
Aha, this is related to #57 - it says "not possible"...... |
In the AuditLoggingGrailsPlugin descriptor, we register an AuditLogListener per DataSource. In the AuditLogListener, you need to figure out if the Domain object is tenant enabled and store the AuditTrail using this tennant id. Maybe 11.2.3 in Gorm 6.1 docs can be a hint. Please note that the plugin must stay ORM agnostic. So you need to find an ORM independent way. Thus, don't deal with Hibernate / Mongo / etc. classes directly. Haven't played around with tenancy yet, so the info above is just a rough guess. |
Do we have support for multitenancy now? |
Hi, we are implementing an application which uses the GORM multitenancy in DATABASE mode, e.g.
However, the audit-logging plugin ignores the resolved tenant data source and always writes to the DEFAULT data source.
Could you add support for multitenancy?
The text was updated successfully, but these errors were encountered: