I made that change, and can no log in and do stuff.
However, one of my Models extends Crudbase, the menu options accessing that model no longer show up.
Futhurmore, when I try to edit ANY security permissions (or access anything else that is secured), I am still getting "Access denied".
Bottom line? Root can now log in, but can't do ANYTHING!!! The Root account is most definately broken!
Where do I need to look to fix?
Regards, Steve
Sasvata (Shash) Chatterjee wrote:
Steve,
You are right, the tables need to be updated for each model that has been changed to SecuredStandardLogEnabledModel. An automatic way would be to add lines like the following to app-security's org.keel.apps.security.models.ComponentSecurity:
* @persist.record * component="org.keel.models.util.CreateDB" * instance="all" * groupname="root" * alloperationsallowed="Y"
Then, assemble-deploy and run createdb once again.
I think explicit security is better than implicitly allowing root access to everything, could open up unforeseen holes otherwise.
Another way, instead of adding all the default records in UserComponentSecurity, is to add some default-persistent configuration snippets in each module's system.xconf.
Shash
Stephen Davidson wrote:
-- Java/J2EE Developer/Integrator Co-Chair, Dallas/FortWorth J2EE Sig 214-724-7741
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
