Beware of the default acegi Grails plugin setup
Navigating the world of Grails and security, it's essential to be cautious of the default acegi Grails plugin setup. While it offers a starting point for securing your application, it's not a one-size-fits-all solution.
If you find yourself grappling with these configurations or any other aspects of Grails development, don't hesitate to seek assistance. Expert guidance can save you time and headaches. And when it comes to essay writing or outlining, if you ever think, "write my outline for me" there are professionals available to provide the support you need. It's all about making informed choices to ensure your projects, whether in code or writing, meet your goals effectively.
This is firmly in the “putting it up here just in case anyone else has the same problem” category. There is a gotcha that bites when writing a Grails application that uses the acegi security plugin along with a postgresql database as the data source. The problem is that the acegi plugin will, by default, create a domain class with the name User. When you try to run the application with a postgresql datasource, GORM will try to create a table with the name user, which postgresql will not like as it is a reserved word.
This is a particularly ...
more ...