|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
Packages that use org.janux.bus.security | |
---|---|
org.janux.bus.security | The org.janux.bus.security package, soon to be renamed the org.janux.authorization package, contains interfaces that define a very flexible Permission-Based scheme for doing Authorization within an application; this scheme makes it possible to define whatever permissions suit a specific domain, and aggregate them into existing or new roles without having to make code changes; the key interfaces of this package are PermissionsCapable , Account , Role , and PermissionContext . |
Classes in org.janux.bus.security used by org.janux.bus.security | |
---|---|
Account
Represents a login account in the application, could also have been called a User or a Principal, see more below. |
|
AccountFacet
|
|
AccountParty
|
|
AccountPartyFacet
|
|
AccountSetting
This is a temporary interface to store account settings that will be deprecated in favor of the more general interfaces in the org.janux.adapt package |
|
PermissionBit
Class representing an individual PermissionBit within a specific PermissionContext; a PermissionBit is only meaningful in the context of the PermissionContext that defines it: for example, a PermissionContext named 'PERSON' may define Permissions with names 'CREATE', 'READ', 'UPDATE', 'DISABLE', 'PURGE', that define the kind of operations on Persons that may be restricted by the security system; see the javadoc of PermissionContext for a more detailed discussion. |
|
PermissionContext
A PermissionContext represents a set of individual Permissions defined for a specific business context; for example, a PermissionContext named 'PERSON' may define five Permissions with names 'READ', 'UPDATE', 'CREATE', 'DISABLE', 'PURGE', that define the kind of operations on Persons that may be restricted by the security system. |
|
PermissionsCapable
This interface defines classes that may have permissions granted to them; as of this writing, it is intended to be a super interface for the Account and Role interfaces, both of which may be assigned Permissions directly. |
|
Role
Roles are hierarchical constructs that aggregate Permissions and other Roles and make it possible to compose a base set of Permissions in the following manner: a ROLE_PRODUCT_MANAGER Role may be created comprising Create/Read/Update/Delete Permissions to Product objects a ROLE_CONTENT_MANAGER may be created comprising Create/Read/Update/Delete Permissions to marketing content, a ROLE_STORE_MANAGER may be created that encompasses all Permissions of the ROLE_PRODUCT_MANAGER AND ROLE_CONTENT_MANAGER a ROLE_SUPERVISOR may be created that encompasses the ROLE_STORE_MANAGER plus the permission to publish content. |
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |