At the moment it needs developer to write an adaptor class (which extends from ActAAAService.Base) and implement a few methods to bridge Act with osgl-aaa.
The proposal is to define a few utilities so it can save the developer from writing the adaptor class:
UserModelBase, which implement org.osgl.aaa.Principal directly
Provide a few annotation so user can easily their own UserModel to a Principal data provider:
@PrincipalEntity - mark a user model class
@RoleProvider - mark a method that returns a Role name list
@PermissionProvider - mark a method that returns a permission name list
@PrivilegeProvider - mark a method that returns privilege name or level
@PasswordVerifier - mark a method that verify password with the user's password hash
Allow developer to specify the above information from configuration file. This is useful when UserModel comes from a third party library.
An AuditBase to be extended by app's Audit record
UserLinked interface along with a DynamicPermissionChecker which create default row level authorisation
At the moment it needs developer to write an adaptor class (which extends from
ActAAAService.Base) and implement a few methods to bridge Act with osgl-aaa.The proposal is to define a few utilities so it can save the developer from writing the adaptor class:
UserModelBase, which implementorg.osgl.aaa.Principaldirectly@PrincipalEntity- mark a user model class@RoleProvider- mark a method that returns a Role name list@PermissionProvider- mark a method that returns a permission name list@PrivilegeProvider- mark a method that returns privilege name or level@PasswordVerifier- mark a method that verify password with the user's password hashAuditBaseto be extended by app's Audit recordUserLinkedinterface along with aDynamicPermissionCheckerwhich create default row level authorisation