VOMS Awareness Sample Clauses
The VOMS Awareness clause serves to ensure that all parties are informed about the Vendor Order Management System (VOMS) and its role in the contractual relationship. Typically, this clause requires parties to acknowledge their understanding of how VOMS will be used for order placement, tracking, and communication regarding goods or services. By including this clause, the agreement clarifies expectations around the use of VOMS, reducing the risk of misunderstandings and ensuring smooth operational processes.
VOMS Awareness. DPM has full voms-awareness. There are access controls on pools, spaces and the namespace. Of course only the namespace is POSIX, the others are somewhat simpler lists, but they do take VOMS FQANs into account.
VOMS Awareness. StoRM has full voms-awareness. An improvement on the permissions management will be provided. There will be the possibility to define ACLs on a per-directory base. These ACLs will also be based on DNs and FQANs and will allow for wildcards.
VOMS Awareness. Since access control is delegated to the CASTOR instance it is not proposed that the CASTOR SRM will me made fully VOMS aware as defined within the scope of this document. To attempt to do so would lead to operations teams having to maintain both castor and srm protections and ensuring they are consistent at all times. It may be possible to implement restrictions on specific SRM APIs to VOMS roles, but this is outside the scope of this document. In the next three months an administrative interface will be made available for CASTOR administrators to easily set white and black lists.
VOMS Awareness. Since access control is delegated to the CASTOR instance it is not proposed that the CASTOR SRM will be made VOMS aware as defined within the scope of this document before the CASTOR backend itself is made VOMS aware. To attempt to do so would lead to operations teams having to maintain both CASTOR and SRM protections and ensuring they are consistent at all times. It may be possible to implement restrictions on specific SRM APIs to VOMS roles, but this is outside the scope of this document. The current plan is to implement VOMS primary role based authentication in CASTOR for Q1 2009, and a fully VOMS awareness of CASTOR and the SRM interface is envisaged for Q3 2009.