Security Technology: JAAS, acegi Security System

Acegi security system utilizes the IOC and AOP mechanisms provided by spring to implement a security architecture that completely decouples our business logic and security check logic, all security logic can be implemented by defining the standard configuration file of spring.

• The configuration file of acegi security system uses spring standard configuration. To some extent, its configuration is intended for users who have a good understanding of acegi design and implementation, rather than for end users. There are so many classes in the configuration file that complicated object association can only be seen in the cloud without in-depth understanding of acegi design. Maybe we can package a layer on acegi security to define our own configuration file to simplify acegi security. But think about it. The design of acegi security makes sense. Security is not a simple task. We cannot expect a newbie to complete all security configurations. However, using spring configuration files can achieve maximum flexibility. Using spring's IOC mechanism, all configurations can provide our custom implementation. Once we have a deep understanding of acegi, all these configurations will become natural.

• Acegi documentation is quite good. It deeply analyzes the internal implementation of acegi, the association between classes, and the implementation objectives. However, it ignores that the entire document is designed rather than based on requirements. The entire document seems to be more focused on how acegi security is designed, rather than how it is used. Of course, I admit that if we want to have a deep understanding of acegi, we must know its design and implementation, but for a newbie, if we can immediately know what the acegi security authentication process is like, how can I describe authentication and authorization through an authentication process?

xmlns: DC = "http://purl.org/dc/elements/1.1/"
xmlns: trackback = "http://madskills.com/public/xml/rss/module/trackback/">
RDF: About = "http://fantasy.myserver.org/confluence/pages/viewpage.action? Pageid = 368 "
DC: identifier =" http://fantasy.myserver.org/confluence/pages/viewpage.action? Pageid = 368 "
DC: Title =" Security Technology: JAAS, acegi Security System "
trackback: ping = "http://fantasy.myserver.org/confluence/rpc/trackback/368"/>

--> root decorator: all decisions about how a page is to be decorated via the
inline decoration begins here.
--> switch based upon the context. however, for now, just delegate to a decorator
identified directly by the context.
-->