Ned, I went through the same type of situation and came to the simple conclusion, wicket security just does not cut it for complicated security structures. In the end I rolled my own and it seems to work quite nice. I think the only difference between what I did and you are saying is that my application couldn't create permissions on the fly, basically there is a defined set of createBlah, editBlah permissions that were attached to extended security components, ie links...but from there the users of the application could create as many roles attached to as many different permissions as needed.
Ned Collyer wrote: > > With wicket security (either wasp/swarm, or wicket-auth-roles) can things > like Roles and Permissions be created through a web interface? > > Eg, > I need a system whereby I can add new roles (or principals) through the > web interface, and define their permission to a ACLs which are determined > by which which plugins the system is configured to use. > > Each plugin will implement some interface, and expose the ACLs that it has > available. - these will not be manually configured, and should not require > any java code change when I add a plugin to the system. > > I'm having trouble mapping this to either swarm or wicket-auth-roles. (and > trouble explaining it well ;)) > > I believe wicket-auth-roles is more component oriented, but reading about > this stuff makes my head swim. > > Can anyone either steer me in the right direction, or point at an example > that gets these ACLs and roles from a datastore at run time. > -- View this message in context: http://www.nabble.com/Wicket-Security---runtime-ACLs-and-Roles-help-plz-tp15115011p15141818.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
