JSecurity Plugin

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: 0.4
• Component/s: None
• Labels:

  None

The adding of support for WildcardPermission is half done.
I'm attaching a patch with the rest of the implementation. This patch includes:
-> A modification at JsecDbRealm artifact template so that it knows which JsecUserPermissionRel properties should be passed in to the permission constructor.
-> A modification at JsecDbRealm artifact template so that the SimpleAccount is created with a JsecUser instead of the username, this allows better use of <jsec:principal /> taglib.
-> A modification at JsecurityGrailsPlugin.accessControlMethod(). When no closure is received the access control by convention now uses a wildcard permission this way:
new WildcardPermission("${filter.controllerName}:${filter.actionName ?: 'index'}")
And this permission is what is checked.
-> A modification at JsecurityFilters to allow the mixing of Permission instances and String permissions at the accessControl blocks on controllers.

1. 

   grails-jsecurity.patch

   08/Jan/09 9:45 AM

   21 kB

   Oliver Hernàndez Valls

• Assignee:

  Peter Ledbrook

  Reporter:

  Oliver Hernàndez Valls

• Created:

  08/Jan/09 9:45 AM

  Updated:

  25/Mar/11 1:37 AM

  Resolved:

  05/Aug/09 6:50 AM