Abstract:
Embodiments of the present invention address deficiencies of the art in respect to access control and provide a method, system and computer program product for access control management for a composite application. In a first embodiment, a method for role-based access control management for a composite application can be provided. The method can include selecting a component for deployment in a composite application and parsing a security policy for the component to identify a mapping between a specific role for the component and a virtual role for the composite application. Binding logic can be generated from the security policy and the component can be deployed into the composite application. Finally, security access operations for the virtual role can be processed through method calls to operations defined in the binding logic.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     1. Field of the Invention  
         [0002]     The present invention relates to the concurrent display of multiple, heterogeneous application components and middleware components and more particularly to access control among multiple, heterogeneous application components and middleware components.  
         [0003]     2. Description of the Related Art  
         [0004]     Access control relates to the moderation and limitation of access rights to resources in a computing system. Resources can range from documents to application logic and access rights can range from read-only access to full read, write and execute access. Oftentimes, access control can vary from user to user or group to group depending upon the trustworthiness of the user or group. Those having a higher level of trust are granted access permissions associated with a high degree of access, while those having a lower level of trust are granted only an amount of access permission required to achieve a specific objective. In this way, the exposure of the security and integrity of the underlying resources can be minimized.  
         [0005]     Access control for an application having only a limited number of users can be relatively manageable. For each individual user, a requisite level of access can be determined subjectively, and corresponding access rights can be assigned to the user. For an application which involves a vast number of often unpredictable individual users, access control can be unmanageable. Where the requisite access rights to various resources change for individual users in the latter scenario, access control, administration becomes a very complex task. This increasing complexity also increases the probability for access control mis-configurations to occur, compromising system security. To reduce complexity and its associated risk, system designers have introduced the mechanism of role-based access control.  
         [0006]     Role-based access control relates to the assignment of access rights not to an individual user, but to a role fulfilled by one or more individual users. Specifically, it can be more readily determined what level of access rights are to be afforded to a user who fulfills a particular role in an application, such as an administrator, guest, manager, executive and the like. In the concept of workflow, roles can be extended to the type of user responsible for a portion of a business process. In this way, though the identity and roles assumed by any one user can be fluid in nature, the access rights afforded to a user assigned to a specific role can remain relatively static. Consequently, the management of access rights, even for a vast number of users, can be dramatically simplified.  
         [0007]     Role-based access control solutions have been proposed for a variety of software systems. For simple systems, where a single application executes on a single middleware component, role-based access control has proven to be a powerful tool for mediating access control. Yet, though the use of application roles have been effective in abstracting access control for a simple system, role-based access control has not been effective in managing access control to an aggregation of disparate applications and/or middleware components—especially where the role-based access control systems vary from application to application and middleware component to middleware component within a composite application (the aggregation of heterogeneous applications).  
         [0008]     Business roles have been proposed as a solution to the authorization problem in the composite application space. Business roles define an arbitrary combination of all application roles available for the composite applications. In this way, the disparate nature of the role-based access control for each application can be harmonized within at least one of the arbitrary combinations. Notwithstanding, it will be apparent to the skilled artisan that the mechanism of the business role is deficient at least in respect to potentially large number of business roles which must be defined to accommodate a set of disparate applications for various business objectives. Managing a large number of business roles can be burdensome. Moreover, the solutions integrator must have a priori knowledge of all of the application roles for the composite applications. Finally, not all business roles are valid and can result in the propagation of contradicting roles within the business roles and more complex access control management.  
       BRIEF SUMMARY OF THE INVENTION  
       [0009]     Embodiments of the present invention address deficiencies of the art in respect to access control and provide a novel and non-obvious method, system and computer program product for virtual role based access control management for a collection of heterogeneous application components and middleware components. In a first embodiment, a data processing system for virtual role based-based access control management for multiple heterogeneous application components and middleware components, including enterprise archives, can include a virtual role framework where the roles definition can be abstract in nature, coupled to a composite application and enabled to manage virtual roles that can be defined by metadata for the composite application.  
         [0010]     The system further can include application components and middleware components coupled to the composite application and a security policy defined for the application components and middleware components. The security policy for a application component or middleware component can map at least one specific role for the application component or middleware component to a corresponding virtual role for the composite application. Finally, the invention can produce binding logic derived from the security policy, the binding logic providing an interface for the virtual role framework to operations for the specific role of the middleware component.  
         [0011]     The abstract virtual role meta-model allows for the definition of an arbitrary number of virtual roles. The virtual role product provider can include several exemplary pre-defined virtual roles such as an administrator virtual role and an operator virtual role; but, the virtual role meta-model allows product consumers to define virtual roles to suit the needs of respective composite applications. Yet further, the security policy can be a metadata model disposed in a descriptor for the application component or middleware component. As such, the binding logic can include program code generated by an metamodel-driven code generation tool such as the Eclipse(TM) Modeling Framework (EMF) (Eclipse is a trademark of the Eclipse Foundation) which utilizes the data model of the security policy. Finally, the virtual roles can provide a virtual role-based security framework for the application components and middleware components, category-based security (defined via common access category in multiple applications) for the composite application and the application components and middleware components, and graphical user interface based security for the composite application.  
         [0012]     In another embodiment of the invention, a method for role-based access control management for composite applications can be provided. The method can include selecting an application component or middleware component for deployment in a composite application and parsing a security policy for the middleware component to identify a mapping between a specific role for the middleware component and a virtual role for the composite application. Binding logic can be generated from the security policy and the application component or middleware component can be deployed into the composite application. Finally, security access operations for the virtual role can be processed through method calls to operations defined in the binding logic.  
         [0013]     Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed. 
     
    
     BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS  
       [0014]     The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:  
         [0015]      FIG. 1  is a pictorial illustration of a data processing system configured for virtual role-based access control management of a composite application consisting of multiple heterogeneous application components and middleware components; and,  
         [0016]      FIG. 2  is a schematic illustration of a data processing system for virtual role based access control management of a composite application consisting of multiple heterogeneous application components and middleware components; and,  
         [0017]      FIG. 3  is a flow chart illustrating a process for deploying a component in a data process system configured for virtual role-based access control management for multiple heterogeneous application components; and,  
         [0018]      FIG. 4  is a flow chart illustrating a process for accessing security logic in a component in a data process system configured for virtual role-based access control management for multiple heterogeneous application components. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0019]     Embodiments of the present invention provide a method, system and computer program product for virtual role-based access control management for multiple heterogeneous application components and middleware components, collectively “components”, through the use of a virtual role. A virtual role can be abstract and represents an aggregation of a set of various application roles based upon the common function and responsibility for each role. The virtual roles meta-model provides a means for defining arbitrary virtual roles as per the needs of the composite application. Virtual role names and actions can be mapped to one or more corresponding application component/middleware names and role names and actions on resources. Finally, the virtual framework can generate binding code based on the aforementioned mappings.  
         [0020]     In accordance with an embodiment of the present invention, one or more virtual roles can be established for a composite application such as a portal application. Subsequently, a security policy can be specified for an application or middleware component to be deployed in the composite application, for example a portlet application component or a middleware component. The security policy can relate one or more of the established virtual roles to corresponding roles for the component. As such, binding logic can be generated to relate calls to the operations of the virtual roles to those of the component. Finally, the component can be registered for use in the composite application.  
         [0021]     In further explanation,  FIG. 1  is a pictorial illustration of a data processing system configured for virtual role-based access control management for a composite application composed of multiple heterogeneous application components and middleware components. As shown in  FIG. 1 , one or more components  140  within a composite application  120  can include both a security policy  150  and binding logic  160 . The security policy  150  can map roles specific to the components  140  to corresponding virtual roles  130  defined for the composite application  120 . The binding logic  160 , in turn, can be generated from the security policy  150  in order to provide a gateway interface from users  110  interacting with the composite application  120  to the operations of the specific roles for the components  140 .  
         [0022]     More specifically,  FIG. 2  is a schematic illustration of a data processing system for virtual role based access control management for composite applications consisting of multiple heterogeneous application components and middleware components. As shown in  FIG. 2 , composition logic  210  acting as an aggregator can include a virtual role framework  220 . The virtual role framework  220  can include a selection of security roles for all pluggable components  240  in a composite application  260  produced by the composition logic  210 . Each component  240  in the composite application  260  can include a security policy  250 . The security policy  250  can be a structured data model which maps the security virtual roles to corresponding specific roles for the component  240 .  
         [0023]     Using the security policy  250 , binding logic  230  can be generated. Specifically, code generation technologies, such as an Eclipse Modeling Framework (EMF) code generation tool, can process the structured data model defined by the security policy  250  to produce the binding logic  230 . The binding logic  230  can include security access classes and corresponding methods for the specific roles of the component  240 . In this way, an end user authenticating to a virtual role managed by the virtual role framework  220  in the composition logic  210  can authenticate to the component  240  by way of the binding logic  230  without having an awareness of the specific roles of the component  240 .  
         [0024]     The use of virtual roles in the present invention provides for role-based security as provided by the mapped specific roles of the component  240 . Also, the use of virtual roles provides for category based security in that different virtual roles can relate to different categories of user such as administrator, monitor, operator, configurator, user and the like. Finally, the virtual roles of the present invention can provide for graphical user interface based security in that the display of the composite application  260  can vary depending upon the virtual role assigned to an interacting end user, irrespective of the specific role of a component  240  mapped to the virtual role.  
         [0025]     In further illustration,  FIG. 3  is a flow chart illustrating a process for deploying a component in a data process system configured for virtual role-based access control management for multiple heterogeneous applications. Beginning in block  310 , one or more specific application roles can be defined for a component based upon one or more corresponding virtual roles within the virtual role framework for an aggregated application. Examples can include an administrator role, a monitor role and a user role. In block  320 , a descriptor for the component can be parsed to identify a security policy for the component.  
         [0026]     In block  330 , the syntax for each role declared within the security policy can be verified as well-formed and valid within the virtual role framework. In decision block  340 , if the syntax is verified as incorrect, in block  350  an incompatibility with the declared role for the component can be reported. Otherwise, in block  360  binding logic can be generated for the declared roles within the security policy. For example, the data model represented by the security policy can be passed to an EMF tool to generate the requisite classes and methods for accessing the specific role for the component. Finally, in block  370 , the composite application can be updated to recognize the new component.  
         [0027]     Once the component has been deployed into the composite application, access requests to the component can be managed through the virtual role framework in association with the virtual role assigned to interacting users and not in association with specific roles assigned to interacting users in respect to the component. Specifically, required interactions with the access classes and methods for the specific role of the component can be provided by the virtual role framework utilizing the binding logic produced for the security policy for the component.  
         [0028]     In illustration,  FIG. 4  is a flow chart illustrating a process for accessing security logic in a component in a data process system configured for virtual role-based access control management for multiple heterogeneous components. Beginning in block  410 , a security access operation can be triggered in the aggregated application. In block  420 , a first component deployed in the aggregated application can be selected and in block  430 , the binding logic of the selected component can be checked for the triggered operation. In decision block  440 , if the operation is located within the selected component, in block  450  the operation in the component can be invoked through the binding logic. Otherwise, the process can continue through decision block  460 .  
         [0029]     In decision block  440 , if the required operation cannot be located for the component, in decision block  460  it can be determined if additional components are deployed in the aggregated application. If so, in block  470 , a next component can be selected for analysis and the process can repeat in blocks  430  through decision block  460 . By comparison, in decision block  460 , when no further components remain to be analyzed, the process can end in block  480 .  
         [0030]     Embodiments of the invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, and the like. Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system.  
         [0031]     For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk—read only memory (CD-ROM), compact disk—read/write (CD-R/W) and DVD.  
         [0032]     A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.