Readers of this blog and people on the grails user list noted some difficulties with UTF encoding with the previous release of the stark security plugin. I’m happy to announce this bug-fix release (version 0.4.2) which takes care of the UTF encoding problem, and also fixes another defect related to moving the User and Role domain classes into packages.
Please give it a whirl and let me know if you have any comments and/or questions!
Docs and release notes are here: http://www.grails.org/Stark+Security+Plugin
Mike | 24-Mar-09 at 5:52 am | Permalink
Hi Ola,
thanks for the great plugin! I love the approach it takes. Do you have any plans on releasing a version compatible with Grails 1.1? I would love to upgrade, but there are still some plugin issues giving me headache.
Best regards,
Mike
Ola Bildtsen | 26-Mar-09 at 3:46 pm | Permalink
Thanks for the note, Mike. The plugin version 0.4.2 is released and compatible with grails 1.1 — are you having specific issues with installing it?
Douglas Hahn | 04-Nov-09 at 11:50 am | Permalink
Been playing with grails a few days and came across your plugin. Any thoughts on how I could make this work with MS SQL. user is a reserved word and would need to be surrouned by brackets [user] to work. Do you now of anyway I could change the table name it uses? Is that defined anywhere globally?
-Doug
Ola Bildtsen | 04-Nov-09 at 12:01 pm | Permalink
Doug,
This should be a rather simple change: the only two classes that know about the User class is the User class itself and UserLookupService. Renaming the User class and the references to it in UserLookupService should be all you need to do.
If you’d like to keep the class named ‘User’ but just map it to a different table, you can just add something like this to the ‘mapping’ section in the User.groovy class:
table 'person'
Please let me know if you run into issues.