-
Notifications
You must be signed in to change notification settings - Fork 7
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
Document or fix classes to be tenant aware (GORM 6 multitenancy) #5
Comments
I simplified the solution to this, at least for the password and refresh token flows (along with the typical access token resource protection). Only two classes needed to be overridden, and they do not have transactional annotations so it is much simpler. Also, none of the classes need methods implemented since they can just call the super class.
|
To get this working, I had to override the default token store and provide my own implementation that was a direct copy of the GormTokenStoreService with two modifications:
It looks like the transactional annotation does its work before the CurrentTenant one (which is probably a bug and should be filed with Grails? Or maybe the order of the annotations matter here? I don't know), and causes problems.
It's possible that if we move the Transactional annotations to the class methods in the implementation in this plugin, a tenant aware version would be very simple to just extend and add the CurrentTenant annotation.
The text was updated successfully, but these errors were encountered: