Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences

Edit this page


Referenced by
AppFuseAcegiACL
AppFuseAcegiACLAddAC...




JSPWiki v2.2.33

[RSS]


Hide Menu

AppFuseAcegiACLChangeLinkToManager


Step VI: Change all references to the old manager to the new manager

In this step we need to make sure that only the new (secure) manager is used...

There are 2 different ways to do this:

  1. Change the name of the old manager to "personManagerUnsecure" (Fix also the "ref" tag in the personManagerSecure) and change the id of the personManagerSecure to personManager
  2. Find all bean definitions referenzing the bean "personManager" and hange the bean name to personManagerSecure

Test the app

If you deploy your application, you can test the first part of the ACLs.
  • Login as "mraible" and go to the personList view
  • You should see one person and you should be able to edit / delete this person

And now the ACLs:

  • Login as "tomcat"
  • Goto the person list view: You should see NO persons! This is because the user "tomcat" has no permission at all on the object Person:1, and the role "user" has also no rights on this object.

If you try to add a person, you will be able to save a new person, but the new person will not appear in the person list. this is because we set no ACLs on new objects. We will do this in the next step:

Next step

Step VII. How to create new ACLs


Go to top   Edit this page   More info...   Attach file...
This page last changed on 06-Nov-2006 13:53:00 MST by PeterSchneider-Manzell.