Gonzalo Diethelm wrote:
Hi,Speaking of this topic, I had an idea one night about security. After a couple hours I came up with this:
http://dan.envoisolutions.com/jasf/
It seems to be pretty flexible, but I'm not sure everyone would like using it. I wanted something where I could authenticate not only webpages, but other resources - such as access to various components in my system. I even wrote a XML user and permission based system for it.
Thoughts?
I like it. How do you specify the controllers you want to use? I'm thinking from the point of view of a Turbine security service, you would probably want to configure that from the properties file. In fact, I think it works pretty much like the thing I came up with. Good work! ;-)
Sorry it has taken so long for me to reply, I am currently travelling through Europe :).
To access the different controllers you register them with the ResourceManager or the EntityAuthenticationManager (more correctly the implementation of these interfaces). Then you just do manager.lookup(ResourceClass.RESOURCE_TYPE) or manager.lookup(BasicUser.ENTITY_TYPE). I haven't created binding class for Turbine yet, but yes, it would be through TR.props.
If people are interested (please give me your thoughts) I will port the db service to this as well as finish off an XML implementation that I started as well as create a Turbine binding. If people are seriously considering this I will clean everything up and present as a package in a week or two.
- Dan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
