Implementing role based security in an enterprise content management system

1. A computer implemented method of implementing role based security in an enterprise content management system comprising:

creating, using a processor, a role object;

creating, using the processor, a role adapter object that is communicatively coupled to the created role object;

creating, using the processor, a class for the role adapter object;

creating, using the processor, a security adapter object that is communicatively coupled to the created role adapter object;

adding, using the processor, a security proxy property link to role object;

adding, using the processor, a security proxy property link to the security adapter object;

mapping, using the processor, one or more complex permissions from the role object to one or more primitive permissions;

creating, using the processor, an Access Control List (ACL) based on the mapped primitive permissions, one or more members assigned to a role, and a content class associated with the role;

associating, using the processor the security adapter object to the content class; and

instantiating, using the processor, the role adapter object using a program.

2. The method of claim 1 , wherein creating the role object further comprises:

creating, using the processor, a class for the role object;

adding, using the processor, one or more members from the role;

adding, using the processor, one or more complex permissions from the role;

adding, using the processor, one or more security proxy property links to one or more respective role adapter objects based on the role adapter object being associated with the content class; and

instantiating, using the processor, the role object.

3. The method of claim 1 , wherein creating the security adapter object further comprises:

creating, using the processor, a class for the security adapter object;

adding, using the processor, a security proxy property link from the security adapter object to one or more role adapter objects;

adding, using the processor, a security proxy property link to the content class; and

instantiating, using the processor, the security adapter.

4. The method of claim 1 , wherein:

the content class inherits security definitions from the role object based on the content class being associated with the security adapter object through the security proxy property in the content class;

the security adapter object passes security definitions from the role adapter to the security adapter object through the security proxy property in the security adapter object; and

the one or more role adapter objects is mapped to the role object.

5. The method of claim 1 , wherein:

the content class is a security child of the security adapter object;

the security adapter object is a security child of the role adapter object; and

one or more role adapter objects is mapped to the role object.

6. The method of claim 1 , wherein the content class inherits security definitions in response to the role object being created or modified.

7. The method of claim 1 , wherein the content class includes:

a folder class; a record class; a document class; a link class; and a custom class.

8. A computer program product for implementing role based security in an enterprise content management system, the computer program product including a content manager embodied on a computer readable storage device, the content manager including code executable by a processor to perform a method comprising:

creating a role object;

creating a role adapter object that is communicatively coupled to the created role object;

creating a class for the role adapter object;

creating a security adapter object that is communicatively coupled to the created role adapter object;

adding a security proxy property link to the associated role object:

adding a security proxy property link to the associated security adapter object;

mapping one or more complex permissions from the role object to one or more primitive permissions;

creating an Access Control List (ACL) based on the mapped primitive permissions, one or more members assigned to a role, and a content class associated with the role;

associating the security adapter object to the content class; and

instantiating the role adapter object.

9. The computer program product of claim 8 , wherein creating the role object further comprises:

creating a class for the role object;

adding one or more members from the role;

adding one or more complex permissions from a role;

adding one or more security proxy property links to one or more respective role adapter objects based on the role adapter object being associated with the content class; and

instantiating the role object.

10. The computer program product of claim 8 , wherein creating the security adapter object further comprises:

creating a class for the security adapter object;

adding a security proxy property link from the security adapter object to one or more role adapter objects;

adding a security proxy property link to the content class; and

instantiating the security adapter.

11. The computer program product of claim 8 , wherein:

the content class inherits security definitions from the role object based on the content class being associated with the security adapter object through the security proxy property in the content class;

the security adapter object passes security definitions from the role adapter to the security adapter object through the security proxy property in the security adapter object; and

the one or more role adapter objects is mapped to the role object.

12. The computer program product of claim 8 , wherein:

the content class is a security child of the security adapter object;

the security adapter object is a security child of the role adapter object; and

one or more role adapter objects is mapped to the role object.

13. The computer program product of claim 8 , wherein the content class inherits security definitions in response to the role object being created or modified.

14. The computer program product of claim 8 , wherein the content class includes:

a folder class; a record class; a document class; a link class; and a custom class.

15. A computer system for implementing role based security in an enterprise content management system, the computer system comprising one or more processors, one or more computer-readable storage devices, and a plurality of program instructions stored on at least one of the one or more computer-readable storage devices for execution by at least one of the one or more processors, the plurality of program instructions comprising:

program instructions to create a role object;

program instructions to create a role adapter object that is communicatively coupled to the created role object;

creating a class for the role adapter object;

program instructions to create a security adapter object that is communicatively coupled to the created role adapter object;

adding a security proxy property link to the associated role object;

adding a security proxy property link to the associated security adapter object;

mapping one or more complex permissions from the role object to one or more primitive permissions;

creating an Access Control List (ACL) based on the mapped primitive permissions, one or more members assigned to a role, and a content class associated with the role; and

program instructions to associate the security adapter object to the content class, wherein the content class inherits security definitions in response to the role object being created or modified.

16. The computer system of claim 15 , wherein creating the role object further comprises:

creating a class for the role object;

adding one or more members from the role;

adding one or more complex permissions from the role;

adding one or more security proxy property links to one or more respective role adapter objects based on the role adapter object being associated with the content class; and

instantiating the role object.

17. The computer system of claim 15 , wherein creating the security adapter object further comprises:

creating a class for the security adapter object;

adding a security proxy property link from the security adapter object to one or more role adapter objects;

adding a security proxy property link to the content class; and

instantiating the security adapter object.