ome.security.basic

Class BasicACLVoter

java.lang.Object

ome.security.basic.BasicACLVoter

All Implemented Interfaces:

ACLVoter

public class BasicACLVoter
extends Object
implements ACLVoter

Since:

3.0-M3

Version:

$Revision$, $Date$

Author:

Josh Moore, josh.moore at gmx.de

See Also:

Token, SecuritySystem, Details, Permissions

Field Summary

Fields

Modifier and Type	Field and Description
protected CurrentDetails	currentUser
protected PolicyService	policyService
protected Roles	roles
protected SecurityFilter	securityFilter
protected SystemTypes	sysTypes
protected TokenHolder	tokenHolder

Constructor Summary

Constructors

Constructor and Description
BasicACLVoter(CurrentDetails cd, SystemTypes sysTypes, TokenHolder tokenHolder, SecurityFilter securityFilter, PolicyService policyService)
BasicACLVoter(CurrentDetails cd, SystemTypes sysTypes, TokenHolder tokenHolder, SecurityFilter securityFilter, PolicyService policyService, Roles roles)

Method Summary

Methods

Modifier and Type	Method and Description
boolean	allowAnnotate(IObject iObject, Details trustedDetails) test whether the given object should be annotatable given the trusted details.
boolean	allowChmod(IObject iObject) test whether the given object can have its Permissions changed within the current security context.
boolean	allowCreation(IObject iObject) test whether the given object should be insertable into the DB.
boolean	allowDelete(IObject iObject, Details trustedDetails) test whether the given object should be deleteable given the trusted details.
boolean	allowLoad(org.hibernate.Session session, Class<? extends IObject> klass, Details d, long id) delegates to SecurityFilter because that is where the logic is defined for the read filter Ignores the id for the moment.
boolean	allowUpdate(IObject iObject, Details trustedDetails) test whether the given object should be updateable given the trusted details.
void	postProcess(IObject object) Gives the ACLVoter instance a chance to act on the IObject after the transaction but before finishing the AOP stack.
Set<String>	restrictions(IObject object) Provide the active restrictions for this IObject.
void	throwCreationViolation(IObject iObject) throws a SecurityViolation based on the given IObject and the context of the current user.
void	throwDeleteViolation(IObject iObject) throws a SecurityViolation based on the given IObject and the context of the current user.
void	throwLoadViolation(IObject iObject) throws a SecurityViolation based on the given IObject and the context of the current user.
void	throwUpdateViolation(IObject iObject) throws a SecurityViolation based on the given IObject and the context of the current user.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

currentUser

protected final CurrentDetails currentUser

sysTypes

protected final SystemTypes sysTypes

tokenHolder

protected final TokenHolder tokenHolder

securityFilter

protected final SecurityFilter securityFilter

policyService

protected final PolicyService policyService

roles

protected final Roles roles

Constructor Detail

BasicACLVoter

public BasicACLVoter(CurrentDetails cd,
             SystemTypes sysTypes,
             TokenHolder tokenHolder,
             SecurityFilter securityFilter,
             PolicyService policyService)

BasicACLVoter

public BasicACLVoter(CurrentDetails cd,
             SystemTypes sysTypes,
             TokenHolder tokenHolder,
             SecurityFilter securityFilter,
             PolicyService policyService,
             Roles roles)

Method Detail

allowChmod

public boolean allowChmod(IObject iObject)

Description copied from interface: ACLVoter

test whether the given object can have its Permissions changed within the current security context.

Specified by:

allowChmod in interface ACLVoter

allowLoad

public boolean allowLoad(org.hibernate.Session session,
                Class<? extends IObject> klass,
                Details d,
                long id)

delegates to SecurityFilter because that is where the logic is defined for the read filter Ignores the id for the moment. Though we pass in whether or not a share is active for completeness, a different ACLVoter implementation will almost certainly be active for share use.

Specified by:

allowLoad in interface ACLVoter

klass - a non-null class to test for loading

id - the id of the object which will be loaded. As opposed to the rest of the object, this must be known.

Returns:

true if loading of this object can proceed

See Also:

ACLEventListener.onPostLoad(org.hibernate.event.PostLoadEvent)

throwLoadViolation

public void throwLoadViolation(IObject iObject)
                        throws SecurityViolation

Description copied from interface: ACLVoter

throws a SecurityViolation based on the given IObject and the context of the current user.

Specified by:

throwLoadViolation in interface ACLVoter

Parameters:

iObject - Non-null object which caused this violation

Throws:

SecurityViolation

See Also:

ACLEventListener#onPostLoad(org.hibernate.event.PostLoadEvent)}

allowCreation

public boolean allowCreation(IObject iObject)

Description copied from interface: ACLVoter

test whether the given object should be insertable into the DB. No trusted details is passed to this method, since for transient entities there are no trusted values. The SecuritySystem implementors will usually call ACLVoter.throwCreationViolation(IObject) if this method returns false.

Specified by:

allowCreation in interface ACLVoter

Parameters:

iObject - a non-null entity to test for creation.

Returns:

true if creation of this object can proceed

See Also:

ACLEventListener.onPreInsert(org.hibernate.event.PreInsertEvent)

throwCreationViolation

public void throwCreationViolation(IObject iObject)
                            throws SecurityViolation

Description copied from interface: ACLVoter

throws a SecurityViolation based on the given IObject and the context of the current user.

Specified by:

throwCreationViolation in interface ACLVoter

Parameters:

iObject - Non-null object which caused this violation

Throws:

SecurityViolation

See Also:

ACLEventListener#onPreInsert(org.hibernate.event.PreInsertEvent)}

allowAnnotate

public boolean allowAnnotate(IObject iObject,
                    Details trustedDetails)

Description copied from interface: ACLVoter

test whether the given object should be annotatable given the trusted details. The details will usually be retrieved from the current state array coming from the database.

Specified by:

allowAnnotate in interface ACLVoter

Parameters:

iObject - a non-null entity to test for update.

trustedDetails - a Details instance that is known to be valid.

Returns:

true if annotation of this object can proceed

allowUpdate

public boolean allowUpdate(IObject iObject,
                  Details trustedDetails)

Description copied from interface: ACLVoter

test whether the given object should be updateable given the trusted details. The details will usually be retrieved from the current state array coming from the database. The SecuritySystem implementors will usually call ACLVoter.throwUpdateViolation(IObject) if this method returns false.

Specified by:

allowUpdate in interface ACLVoter

Parameters:

iObject - a non-null entity to test for update.

trustedDetails - a Details instance that is known to be valid.

Returns:

true if update of this object can proceed

See Also:

ACLEventListener.onPreUpdate(org.hibernate.event.PreUpdateEvent)

throwUpdateViolation

public void throwUpdateViolation(IObject iObject)
                          throws SecurityViolation

Description copied from interface: ACLVoter

throws a SecurityViolation based on the given IObject and the context of the current user.

Specified by:

throwUpdateViolation in interface ACLVoter

Parameters:

iObject - Non-null object which caused this violation

Throws:

SecurityViolation

See Also:

ACLEventListener.onPreUpdate(org.hibernate.event.PreUpdateEvent)

allowDelete

public boolean allowDelete(IObject iObject,
                  Details trustedDetails)

Description copied from interface: ACLVoter

test whether the given object should be deleteable given the trusted details. The details will usually be retrieved from the current state array coming from the database. The SecuritySystem implementors will usually call ACLVoter.throwDeleteViolation(IObject) if this method returns false.

Specified by:

allowDelete in interface ACLVoter

Parameters:

iObject - a non-null entity to test for deletion.

trustedDetails - a Details instance that is known to be valid.

Returns:

true if deletion of this object can proceed

See Also:

ACLEventListener.onPreDelete(org.hibernate.event.PreDeleteEvent)

throwDeleteViolation

public void throwDeleteViolation(IObject iObject)
                          throws SecurityViolation

Description copied from interface: ACLVoter

throws a SecurityViolation based on the given IObject and the context of the current user.

Specified by:

throwDeleteViolation in interface ACLVoter

Parameters:

iObject - Non-null object which caused this violation

Throws:

SecurityViolation

See Also:

ACLEventListener.onPreDelete(org.hibernate.event.PreDeleteEvent)

restrictions

public Set<String> restrictions(IObject object)

Description copied from interface: ACLVoter

Provide the active restrictions for this IObject. See {@link ome.security.policy.PolicyService for further details.

Specified by:

restrictions in interface ACLVoter

Returns:

postProcess

public void postProcess(IObject object)

Description copied from interface: ACLVoter

Gives the ACLVoter instance a chance to act on the IObject after the transaction but before finishing the AOP stack.

Specified by:

postProcess in interface ACLVoter