|Publication number||US7546462 B2|
|Application number||US 10/271,215|
|Publication date||Jun 9, 2009|
|Filing date||Oct 15, 2002|
|Priority date||Oct 18, 2001|
|Also published as||US7080092, US7152204, US7340714, US7516440, US7546606, US7552443, US7721193, US7831655, US20030093402, US20030093403, US20030093470, US20030093471, US20030093575, US20030097345, US20030097574, US20030105884, US20030110315, US20030145047, US20030182452, WO2003034219A1|
|Publication number||10271215, 271215, US 7546462 B2, US 7546462B2, US-B2-7546462, US7546462 B2, US7546462B2|
|Original Assignee||Bea Systems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (109), Non-Patent Citations (54), Referenced by (58), Classifications (20), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims priority to U.S. Provisional patent application No. 60/347,919, filed Oct. 18, 2001, entitled “APPLICATION VIEW,” as well as U.S. application Ser. No. 60/347,901, filed Oct. 18, 2001, entitled “EVENT ADAPTER,” each of which is hereby incorporated herein by reference.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document of the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The following applications are cross-referenced and incorporated herein by reference:
U.S. patent application Ser. No. 10/271,194 entitled “APPLICATION VIEW COMPONENT FOR SYSTEM INTEGRATIONS,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,162 entitled “SYSTEM AND METHOD FOR PROVIDING A JAVA INTERFACE TO AN APPLICATION VIEW COMPONENT,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,244 entitled “SYSTEM AND METHOD FOR INVOKING BUSINESS FUNCTIONALITY FOR A WORKFLOW,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,414 entitled “SYSTEM AND METHOD FOR USING WEB SERVICES WITH AN ENTERPRISE SYSTEM,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,157 entitled “SYSTEM AND METHOD FOR IMPLEMENTING AN EVENT ADAPTER,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,156 entitled “SYSTEM AND METHOD USING A CONNECTOR ARCHITECTURE FOR APPLICATION INTEGRATION,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,047 entitled “SYSTEM AND METHOD FOR IMPLEMENTING A SCHEMA OBJECT MODEL IN APPLICATION INTEGRATION,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,402 entitled “SYSTEM AND METHOD UTILIZING AN INTERFACE COMPONENT TO QUERY A DOCUMENT,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,423 entitled “SYSTEM AND METHOD USING ASYNCHRONOUS MESSAGING FOR APPLICATION INTEGRATION,” by Mitch Upton, filed Oct. 15, 2002.
U.S. patent application Ser. No. 10/271,410 entitled “SYSTEM AND METHOD FOR IMPLEMENTING A SERVICE ADAPTER,” by Mitch Upton, filed Oct. 15, 2002.
The invention relates generally to the providing security in a network environment.
E-commerce has become a major driving factor in the new economy. To be successful in the long-term, e-commerce will require many companies to engage in cross-enterprise collaborations. To achieve cross-enterprise integration, a company must first integrate its internal applications. Using existing technology and tools, application integration can be an expensive proposition. No integration solution exists that is easy to use, affordable, and based on industry standards. Neither does a solution exist that is based on an industry standard infrastructure, has universal connectivity, is capable of massive scalability, and has accessible business process tools.
Application integration to this point has been very inward-focused. Many existing integration systems have not focused on integrating applications between enterprises. Even when integration solutions were used for cross-enterprise integration, the solutions were still narrowly focused and aimed at vertical markets. This inward focus did little to help companies field external business-to-consumer and business-to-business applications, such as applications that can utilize the Internet to generate revenue and reduce costs. The requirement for Internet-enabled applications led to the rise of the application server market. To date, application servers have primarily been used to host external applications targeted at customers and partners. Application servers are themselves packaged applications that, instead of solving a specific problem, are general-purpose platforms that host vertical solutions.
The first attempts at application integration were primarily focused on low-level implementation details such as the format of the data, the byte ordering between machines, and character encoding. The focus on low-level data formats was necessary because, for the first generation of application integration solutions, there were no widely adopted standards for data encoding that could be deployed across multiple vertical applications.
The traditional approach involved connecting individual systems to, in effect, hardwire the systems together. This approach can be complex, as connecting different systems can require an intimate, low-level knowledge of the proprietary technologies of multiple systems.
Present integration systems, which have moved away from “hardwiring” systems together, still suffer from a lack of standards. Each integration vendor typically provides a proprietary solution for application integration, message transformation, message formats, message transport, and routing. Not one of these systems to date has achieved significant market share to enable its technologies to become the de-facto standard. This lack of standards has given packaged application vendors little incentive to integrate these systems with their applications. Further, each of these integration systems or servers has its own proprietary API, such that packaged application vendors cannot leverage development beyond a single integration server. This fragmentation of the integration market has provided little financial incentive for third parties.
Systems and methods in accordance with the present invention can restrict access to a resource such as an enterprise system. An application view component can receive a request from a validated system user, and can configure a security principal for that. The application view component can provide an interface that the user can use to access the resource, providing that user has permission to access the resource. A resource adapter can receive a request or call from the application view, and can use a security principal map to map the security principal to a resource-appropriate principal. The resource adapter can perform a resource sign-on in a manner specific to the resource using the resource-appropriate principal.
Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.
Application integration components can be used to integrate a variety of applications and systems, such as Enterprise Information Systems (EISs). Information technology (IT) organizations typically utilize several highly-specialized applications. Without a common integration platform to facilitate application-level integration, these applications cannot be integrated without extensive, highly-specialized development efforts.
Application integration can utilize adapters to establish an enterprise-wide, united framework for integrating any current or future application. Adapters can simplify integration efforts by allowing each application to be integrated with an application server, instead of requiring that each application being integrated with every other application.
The development and widespread acceptance of standards such as the Java 2 Platform, Enterprise Edition (J2EE) from Sun Microsystems, Inc. of Santa Clara, Calif., as well as the eXtensible Markup Language (XML), has laid the groundwork for a standardized approach to the development of these adapters. Perhaps the most significant of these standards for application integration is the J2EE Connector architecture. The J2EE Connector architecture provides a standardized approach for the development of adapters for all types of applications, from legacy mainframe applications, such as CICS from IBM, to packaged applications such as PeopleSoft, Siebel, and SAP. The adoption of such standards enables businesses to develop adapters that work on any J2EE-compliant application server, for example.
Application integration can build on this standardized approach in an application integration framework by providing a standards-based architecture for hosting J2EE Connector architecture-based adapters. Developers can build J2EE Connector architecture-compliant adapters and deploy these adapters, in the integration framework, to connect enterprise applications to an application server.
In order to integrate the operations of an enterprise, the data and functions of the various enterprise systems in an organization must be exposed. In the J2EE model, EIS functionality is exposed to Java clients using an adapter, also referred to as a resource adapter or connector, according to the J2EE Connector Architecture. Adapters can be constructed that define services and events. A service represents a message that requests a specific action in the EIS. For example, an adapter might define a service named AddCustomer that accepts a message defining a customer and then invokes the EIS to create the appropriate customer record. An event issues messages when events of interest occur in the EIS. For example, an adapter might define an event that sends messages to interested parties whenever any customer record is updated in the EIS.
These adapters can be used to define business-focused interfaces to an EIS, the interfaces referred to herein as “application views” of the respective adapters. An application view can provide a simple, self-describing, consistent interface to services and events in an application. Application views can make use of an adapter for an EIS, making it possible to expose existing information systems as business services. Unlike adapters, however, an application view does not require users to have intimate knowledge of the EIS or the client interface for that EIS, such that non-programmers or technical analysts can use application views. An application view can provide a business-oriented way for business analysts to access enterprise data without worrying about the programmatic details defined in an adapter. These same users may be otherwise unable to use an adapter directly, due to a lack of familiarity with the EIS.
An application integration component directed at enterprise application integration can have several primary aspects. If the functionality of an EIS such as a PeopleSoft system or an SAP system is to be invoked, an implementation of the J2EE Connector Architecture can be used. If something occurs inside an EIS system, such as a trigger going off, an event can be generated. This event may, in some embodiments, need to be communicated to an external application. An event architecture in an application integration component can handle this communication.
An application view can provide significant value to an application integration component. An application view can abstract away much of the complexity in dealing with an application, such as a backend EIS system. Application views can also simplify the way in which adapters are accessed. Application views can provide a layer of abstraction, for example, between an adapter and the EIS functions exposed by that adapter. Instead of accessing an EIS by direct programming a user can simply: edit an adapter's application views, create new application views, or delete any obsolete application view(s). A layer of abstraction formed by application views can help non-programmers maintain the services and events exposed by an adapter. Each application view can be specific to a single adapter, and can define a set of business functions on that adapter's EIS. After an adapter is created, a Web-based interface for the adapter can be used to define application views.
If an application view is used as a primary user interface for an adapter, a number of features can be included that are not commonly found in existing enterprise application integration technologies. Application views can, for example, use XML as a common language among applications. Service and event definitions can be used to expose application capabilities. XML schemas can be used to define the data for services and events. Bidirectional communication can also be supported in adapters.
An application view can be an integral part of an integration framework. An application view can provide a view of the application capabilities exposed by an adapter that a user can customize to meet specific needs. A user can tailor an application view, for example, for a specific business purpose. As a result, the application view can provide an effective alternative to the “one size fits all” approach that many applications provide for the design of a client interface. An application view can be defined for only the business or other capabilities that are applicable for a specific purpose. The capabilities can be customized such as by naming, describing, and defining the data requirements.
In one example of a system using a resource adapter and application view component, shown in
In addition to defining and implementing adapters, an application integration component can enable a developer to create application views. An application view can provide a layer of abstraction on top of an adapter. Whereas adapters are typically closely associated with specific functionality in the EIS, an application view can be associated with business processes that must be accomplished by clients. An application view can convert the steps in the business process into operations on the adapter.
An application view can expose services and events that serve the business process. An application view control can be associated with a particular application view, and can make the services and methods of the application view available to web services as control methods and callbacks. A variable name used to access a new application view control instance from a web service should be a valid Java identifier.
Application integration can utilize an integration framework, which can provide a systematic, standards-based architecture for hosting application views. Features of such a framework can include application views for exposing application functions and design-time graphical user interfaces (GUIs), such as web-based interfaces that can be used for creating application views. The integration framework utilizes adapters, instead of “hardwiring” enterprise systems together. Once an adapter is deployed for an EIS, other components and applications can use that adapter to access data on the EIS.
A framework in accordance with one embodiment of the present invention relies on XML as the standard format for messages. XML includes XSLT, a standard for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In XSLT, an XML document is used to specify the operations to perform on a class of XML documents in order to transform the documents' structure and content. An XSLT transformation can make use of any of the operations built into the Java programming language, or can make use of custom operations written either in Java or in native code. An integration framework allows a business process to invoke an XSLT engine in order to transform XML messages.
An integration framework can also rely on standards for transporting messages such as Java Message Service (JMS) and HTTPS. JMS is a standard API for interfacing with message transport systems. Using JMS, a framework can utilize any message transport mechanism that provides a JMS interface. The J2EE Connector architecture standard does not specify a message transport mechanism, but an application integration framework can specify such a transport mechanism.
An integration framework can be based on an existing standard infrastructure, such as an application server that supports J2EE, JMS, and the J2EE Connector architecture. Using such a standard infrastructure also provides for high availability and scalability, such as by clustering and resource pooling. The framework can provide for universal connectivity by enabling the construction of XML-based application adapters that can connect to any legacy and packaged application. An adapter development kit can be used to allow users such as customers, system integrators, and packaged application vendors to quickly develop J2EE connector architecture-compliant and integration framework-based adapters. The framework can utilize XML, which means that the same data format can be used for both within- and between-enterprise integration, since many e-commerce systems use XML as the standard message format.
An integration framework can also utilize a business-process engine to allow non-programmers to graphically construct and maintain business processes. An integration framework can implement a common model on top of the J2EE Connector architecture that is focused on business-level concepts. This model, which can consist of XML-encoded events and services, allows the management of a consistent integration environment, regardless of the interface required between adapters and their target applications. The business processes can react to events generated by applications, and they can invoke an application's functionality via services that are exposed by an application adapter.
Because an application view provides access to the inner workings of an application, it will often be desirable to limit access through the application view. If more than one level of access is desired, this can require the setting and management of multiple levels of access and security. One embodiment in accordance with the present invention allows methods to be invoked on an application view that allow a security level be set before services are invoked on the application view.
If the BPM component needs to access an enterprise system or other underlying resource through a JCA connector 218, the BPM component 210 can make a call to an application integration component 216, where the principal can be configured by an application view for the application integration component 216. An application integration service can run as the security principal configured for the application view. The JCA component can use a security principal map. When a JCA adapter receives a request, for example, the adapter can map the caller's security principal to one that is appropriate for the EIS system. Once the BPM component 210 has all the necessary information to serve the request, the BPM component can pass the response or message on to another B2B component 214 in communication with the trading partner 220 to receive the response.
Methods such as “setConnectionSpec( )” and “getConnectionSpec( ),” for example, can be used to set the credentials for an EIS using a “ConnectionSpec” object. Credentials can refer to information describing the security attributes (identity and/or privileges) of a user or other principal. Credentials can be claimed through authentication or delegation, and used by access control. To instantiate a ConnectionSpec object, a class such as “ConnectionRequestInfoMap” can be provided. Such a class can be provided through, for example, an adapter development kit (ADK). A user can also implement a unique class created by that user. If a user creates such a unique class, the user may need to include certain interfaces. These interfaces can include, for example: a ConnectionSpec interface or ConnectionRequestInfo interface for a JCA class, a Map interface for an SDK class, and a Serializable interface for an SDK class.
Before using methods such as setConnectionSpec( ) or getConnectionSpec( ), a ConnectionSpec object should be instantiated. A class such as a ConnectionRequestInfoMap class can be used to instantiate a ConnectionSpec object. To implement a ConnectionSpec object, the user can use a pre-existing class such as ConnectionRequestInfoMap class or implement a user-specific class. If implementing a user-specific ConnectionSpec class, certain interfaces should be included. These interfaces can include, for example, ConnectionSpec (JCA class), ConnectionRequestInfo (JCA class), Map (SDK class), and Serializable (SDK class).
After implementing a ConnectionSpec class and instantiating a ConnectionSpec object, the user can take advantage of both with the application view methods such as setConnectionSpec( ) and getConnectionSpec( ). Code for a method such as setConnectionSpec( ) can be given by, for example:
* Sets the connectionSpec for connections made to the EIS. After
* ConnectionSpec is set it will be used to make connections to the
* EIS when invoking a service. To clear the connection spec, and use
* the default connection parameters, call this method using null.
* @params connectionCriteria connection criteria for the EIS.
public void setConnectionSpec(ConnectionSpec connectionCriteria)
m_connCriteria = connectionCriteria;
Similarly, code for a method such as getConnectionSpec( ) can be given by, for example:
* Returns the ConnectionSpec set by setConnectionSpec. If no
* ConnectionSpec has been set null is returned.
* @returns ConnectionSpec
public ConnectionSpec getConnectionSpec()
To set a ConnectionSpec class, it can be passed a properly-initialized ConnectionSpec object. To clear a ConnectionSpec class, it can be passed a ConnectionSpec object with a null value. An example of how to use a ConnectionSpec object can be given by:
Properties props = new Properties(); ApplicationView applicatgionView = new ApplicationView(getInitialContext(props),“appViewTestSend”); ConnectionRequestInfoMap map = new ConnectionRequestInfoMap(); // map properties here map.put(“PropertyOne”,“valueOne”); map.put(“PropertyTwo”,“valueTwo”); //set new connection spec applicationView.setConnectionSpec(map); IDocumentDefinition requestDocumentDef = applicationView.getRequestDocumentDefinition(“serviceName”); SOMSchema requestSchema = requestDocumentDef.getDocumentSchema(); DefaultDocumentOptions options = new DefaultDocumentOptions(); options.setForceMinOccurs(1); options.setRootName(“ROOTNAME”); options.setTargetDocument(DocumentFactory.createDocument()); IDocument requestDocument = requestSchema.createDefaultDocument(options); requestDocument.setStringInForst(“//ROOT/ElementOne”,“value”); requestDocument.setStringFirst(“//ROOT/ElementTwo”,“value”); . . . // the service invocation will use the connection spec set to connect to the EIS IDocument result = applicationView.invokeService(“serviceName”, requestDocument); System.out.println(result.toXML());
Container-Managed and Application-Managed Sign-on
As specified in the J2EE Connector Specification, Version 1.0 Final Release, a J2EE ConnectorArchitecture implementation can support both container-managed and application-managed sign-on. At runtime, a J2EE Connector Architecture implementation can determine the chosen sign-on mechanism. Such determination can be based upon the specified information in the invoking client component's deployment descriptor. If the implementation is unable to determine the sign-on mechanism being requested by the client component, such as may be due to an improper JNDI lookup of the resource adapter Connection Factory, the Connector Architecture can attempt container-managed sign-on. Even in this case, if the client component has specified explicit security information, this information can also be presented on the call to obtain the connection.
With application-managed sign-on, a client component can provide the necessary security information (typically a username and password) when making the call to obtain a connection to an Enterprise Information System (EIS). In this scenario, the application server may otherwise provide no additional security processing other than to pass this information along on the request for the connection. The provided resource adapter would use the client component provided security information to perform the EIS sign-on in a resource adapter-implementation specific manner.
With container-managed sign-on, a client component does not present any security information, and the container can determine the necessary sign-on information and provide this information to the resource adapter when making a call to request a connection. In all container-managed sign-on scenarios, the container can determine an appropriate Resource Principal and provide this Resource Principal information to the resource adapter in the form of a Java Authentication and Authorization Service (JAAS) Subject.
Password Credential Mapping Mechanism
The J2EE Connector Specification, Version 1.0 Final Release defines two types of credentials that resource adapters can support: password credentials and generic credentials. A user can specify password credentials in a security-principal-map element in a ra.xml deployment descriptor file. The security-principal-map element was provided to map between the initiating principal and resource principal. A Password Converter Tool can be used for encrypting the password stored in the security-principal-map element. The storage of user names and passwords for principal maps in the ra.xml file is not the most elegant nor secure storage mechanism, however.
The J2EE Connector specification, Version 1.0 Final Release requires storage of credentials in a javax.security.auth.Subject; the credentials are passed to either the createManagedConnection( ) or matchManagedConnection( ) methods of the ManagedConnectionFactory object. To comply with this, a J2EE Connector Architecture implementation can build the Subject and store the credentials by performing steps such as the following. First, a security.Service.EISResource object can be instantiated as follows:
The Initiating Principal for the connection request can be obtained. The Credentials for that Initiating Principal can also be obtained as follows:
A javax.security.auth.Subject can be instantiated, and the Credentials can be added to the private set in the Subject as follows:
Application/integration server users typically must be authenticated whenever they request access to a protected server resource. For this reason, each user can be required to provide a credential, such as a username/password pair or a digital certificate. Authentication mechanisms can include the following:
Mutual authentication can also be used. In this case, the application/integration server not only authenticates itself, it also requires authentication from the requesting client. Clients can be required to submit digital certificates issued by a trusted certificate authority. Mutual authentication is useful when access is to be restricted only to trusted clients. For example, it might be desirable to restrict access by accepting only clients with digital certificates provided by the entity owning the server.
Users are entities that can be authenticated in a server security realm. A User can be a person or a software entity, such as a Java client. Each User can be given a unique identity within a server security realm. A system administrator can guarantee that no two Users in the same security realm are identical.
Defining Users in a security realm can involve specifying a unique name and password for each User that will access resources in the server security realm. Special users can be provided for use by resource adapters. These special users can include, for example:
A Group can represent a set of Users who usually have something in common, such as working in the same department in a company. Groups can be a means of managing a number of Users in an efficient manner. When a Group is granted a permission in an ACL, all members of the Group can effectively receive that permission. Permissions can be assigned to Groups rather than to individual Users.
Deprecated Security Principal Map Mechanism
The “EIS Sign-on” section of the J2EE Connector Specification, Version 1.0 Final Release identifies a number of possible options for defining a Resource Principal on whose behalf the sign-on is being performed. Previous implementations implemented the Security Principal Map option identified in the specification. Under this option, a resource principal is determined by mapping from the identity of the initiating/caller principal for the invoking component. The resultant resource principal does not inherit the identity or security attributes of the principal that it is mapped from, but instead gets its identity and security attributes (password) based upon the defined mapping.
In order to enable and use container-managed sign-on, it can be necessary to provide a mechanism to specify the initiating-principal to resource-principal association. This can be done through a Security Principal Map that can be defined for each deployed resource adapter.
If container-managed sign-on is requested by the client component and no Security Principal Map is configured for the deployed resource adapter, an attempt can be made to obtain the connection, but the provided JAAS Subject can be NULL. Support for this scenario can be based upon the resource adapter implementation.
A scenario in which omitting configuration of a Security Principal Map might be considered valid is the case in which a resource adapter internally obtains all of its EIS connections with a hard-coded and pre-configured set of security information, and therefore does not depend on the security information passed to it on requests for new connections. This can be considered a third scenario, outside of application-managed sign-on and container-managed sign-on.
While the defined connection management system contracts can define how security information is exchanged between an application server and the provided resource adapter, the determination of whether to use container-managed sign-on or application-managed sign-on can be based on deployment information defined for the client application that is requesting a connection.
Using Container-Managed Sign-On
To use container-managed sign-on, an application server can identify a resource principal and request the connection on behalf of the resource principal. In order to make this identification, the server can look for a Security Principal Mapping specified with the security-principal-map element in a ra.xml deployment descriptor file.
A security-principal-map element can define the relationship of initiating-principal to a resource-principal. Each security-principal-map element can provide a mechanism to define appropriate resource principal values for resource adapter and EIS sign-on processing. The security-principal-map elements can allow the specification of a defined set of initiating principals and the corresponding resource principal's username and password to be used when allocating managed connections and connection handles.
Default Resource Principal
A default resource principal can be defined for the connection factory in a security-principal-map element. Ifan initiating-principal value of ‘*’ is specified and a corresponding resource-principal value, the defined resource-principal can be utilized whenever the current identity is not matched elsewhere in the map. This element can be specified it in some form if container-managed sign-on is supported by the resource adapter and used by any client. In addition, the deployment-time population of a Connection Pool with Managed Connections can be attempted using the defined ‘default’ resource principal if one is specified.
Security Policy Processing
The J2EE Connector Specification, Version 1.0 Final Release defines default security policies for any resource adapters running in an application server. It also defines a way for a resource adapter to provide its own specific security policies overriding the default.
In compliance with this specification, can application server can dynamically modify the runtime environment for resource adapters. If the resource adapter has not defined specific security policies, the server can override the runtime environment for the resource adapter with the default security policies specified in the J2EE Connector Architecture Specification. If the resource adapter has defined specific security policies, the server can first override the runtime environment for the resource adapter first with a combination of the default security policies for resource adapters and the specific policies defined for the resource adapter. Resource adapters can define specific security policies using the security-permission-spec element in the ra.xml deployment descriptor file.
A security architecture can be used to provide for server security and entitlement processing that allows security and business logic plugins to be inserted into a security service hosted by a server. The architecture can also be used to control access to one or more secured resources on that server, on another server within the security domain or realm, or between security realms. The security service can act as a focal point for security enforcement and access rights determination, and information used within one login process can flow automatically to other login processes, allowing for single sign or security enforcement.
A security architecture can allow for the determination of entitlements as used within an access context. A user can attempt to access a protected resource on the server. This protected resource may, for example, be a software application running on the server, a particular Web page or portion of a Web site, or a database system. Other types of protected resources may be used while remaining within the spirit and scope of the invention. When a user attempts to access the resource, the security service can determine the type of access request, the destination (the protected resource), and the context in which the request is made. From this information the security service can determine an entitlement, or a set of entitlements, for the user. Entitlements can denote that which a particular user can accomplish with a particular resource in a particular context. Entitlements can be used to represent the business logic or functionality required by the server provider, thus bridging the gap between a simple security platform, and a complex business policy platform.
A security architecture can also allow for the integration of third party vendor security products to provide protection for such application types as Enterprise Java Beans, Web Applications (Servlets, Java Server Pages (JSP's)), and Resources (Remote Method Invocation (RMI), Java Messaging System (JMS)). An architecture can also allow for the integration of external public key infrastructure to support such advanced features as certificate and key retrieval, certificate validation, and revocation mechanisms (Certificate Revolution List (CRL), Online Certificate Status Protocol (OCSP)).
For many systems, it may be desirable to include support for the Java 2 Enterprise Edition (J2EE) specification and interoperability therewith. These J2EE specification features include the Common Secure Interoperability (CSI) protocol, user identity tokens, the Stateless Authentication Service (SAS) protocol, support for propagation of security credentials across machine, cluster, and/or domain boundaries, control of propagation of identity based on policy, enhanced support for virtual host/sites, the ability to generate a user identity scoped to domain, and host/site specific security policies.
It may also be desirable to include support for features such as updated SSL capabilities, hardware accelerators, Transport Level Security (TLS) protocol, session resumption, certificate authorities, protection of network connections, Web server proxy, server to server communications, encryption of session ID, and enhanced integration with directory servers.
Dynamic Role Association
Dynamic Role Association is a mechanism that can be used to allow a late binding of the association of roles to principals. A role is an organizational identity that defines a set of allowable actions for an authorized user. Dynamic Role Association is capable of taking the context of the request into consideration during the determination of the roles for which the principal is entitled. Dynamic Role Association can be thought of as the late binding of principals to roles at runtime. This late binding can occur just prior to an authorization decision for a protected resource regardless of whether the principal-to-role association is statically defined or dynamically computed. Because of its placement in the invocation sequence, the result of any principal-to-role associations can be taken as identity as part of any authorization decision made as part of this request.
Unlike statically defined associations, the association of principals to roles can be computed dynamically at runtime. The computation of a dynamic role is able to access a number of pieces of information that make up the context of the request, including the identity of the target (if available), the values of the request's parameters, the values of profile attributes associated with the initiating principal, as well as potentially other information.
The context information can be utilized as values of parameters in an expression that is to be evaluated by a rules or expression evaluation engine. Depending upon the functionality provided by the evaluation engine, it may also be possible to express the ability to call out to an external class that performs external calculations, such as the amount of miles flown by the principal, that are then used as parameter of the expression.
In addition to computing any roles that should be dynamically associated with the principals in the Subject, this same functionality also can be responsible for associating any roles that were statically defined either through the consumption of a J2EE defined Deployment Descriptor or by an administrator.
The result of this capability can be, for example, an updated JAAS Subject that contains any roles that the principals contained in the Subject were entitled to receive given the context and the target. These roles can then be available to any authorization decisions on protected resources, as well as business container and application code. For example, a personalization server, application server, or Web server, could utilize standard methods to determine if a particular role is held by the subject as a means to personalize a web page. This same mechanism could be used by an Enterprise Java Bean or other application to determine whether to retrieve certain fields from a record in a database, without having knowledge of the business policies that determine whether access should be allowed, resulting in field-level authorization.
Parametric Authorization is a mechanism that can allow an authorization decision to be determined about a protected resource, which can be based on the context of the request. Within such an architecture, the scope of enforcement can apply to all execution and resource containers. This can be accomplished by having all execution and resource containers obtain authorization and role mapping services through an AccessController object provided by a Security Service. An AccessController can utilize authorization services provided through Service Provider Interfaces in order to provide the requested capabilities.
Service Provider Interfaces (SPIs) can define the mechanisms used to provide Dynamic Role Association and Parametric Authorization. SPIs can be based on a delegated authorization design that results in the point of enforcement being moved to the provider of the functionality, instead of within the application server itself. A Service Provider Interface (SPI) can be a package or set of packages that support a concrete implementation of a subset of services.
In addition, methods defined on the Service Provider Interfaces that comprise the authorization framework can utilize an enforcement mechanism designed to support a capabilities-based authorization mechanism that more naturally aligns with the services provided by 3rd-party authorization vendors. The use of a capabilities-based mechanism can allow the delegated authorization approach to support both capabilities-based as well as permission-based implementations.
In a parametric authorization-based mechanism, the authorization decision can be made using the context of the request, allowing the authorization decision to more closely represent real business decisions. There may be little need for compensating security checks in the application itself. In a real-world banking example, it is possible for the authorization decision to take into consideration the amount of the transfer, the currency of both source and destination accounts, and the day of the week as part of processing the business policy that controls whether transfers are allowed, by whom, and under what circumstances.
Access to Context Information
Providing context information without prior knowledge of a business policy can be accomplished by using callbacks to containers from the authorization provider. While changing the type or number of parameters of a request can fundamentally change the application and require the application be re-deployed, it is possible for the implementations of dynamic role association and parametric authorization providers to obtain access to the context information without requiring the application to have prior knowledge of aspects of the business policies.
Service Provider Interfaces defined to work with the invention and support the authorization framework can utilize a standardized callback mechanism similar to the one defined in the Java Authentication and Authorization Service (JAAS). Utilizing a callback handler that is passed from the container to the implementation of the Service Provider Interfaces, the provider can request that specific context information be returned. When the container's callback handler is called, the container can respond by populating the callbacks with the appropriate values. If the container does not understand the callback specified in the handler, it does not update the callback with a value. Neither the application, nor the container may be aware of changes to business policy since they are queried for context information that is driven by the evaluation of specific business policy expressions.
An entitlement processing engine (entitlement engine) can satisfy the requirements of parametric authorization by utilizing an implementation capable of specifying that the value of a parameter from the business request, primary key, attribute from a Principal contained in the JAAS Subject that represents an authenticated user, and any potentially other information considered part of the context be expressed as part of a rule expression.
An implementation can request parametric information from the caller on-demand, instead of requiring any parametric information that could be potentially used by the evaluation of rules to be passed at the beginning of rule evaluation. The mechanism for requesting information can be in the form of a callback similar to that defined for JAAS. The implementation might call back for each piece of information individually, request multiple pieces of information in a single callback, or a combination of both.
An implementation can also specify the name of a Java class that will be called as part of the evaluation of a rule. The value returned from the Java class will be used in the evaluation of the rule expression. This can be thought of as a macro facility where user provided code is called to compute a value that is then taken into consideration when evaluating the rule. For example in a travel booking example, a rule expression could specify a call to a user-supplied class that computes or looks up the number of miles a passenger represented by the Subject has flown to date.
The evaluating of a set of rules can result in a boolean value that indicates whether the rule was successfully satisfied or not.
A framework architecture can allow application implementations, particularly login, authorization, and auditing implementations, to be deployed or “plugged in” to allow the development of readily adaptable and customizable business functions and scenarios. These systems can serve to interpret the principal identity in the context of a particular scenario, and to tailor business functions to meet the interpreted identity.
A framework architecture can allow Java developers to make use of existing Java security features, as well as to greatly expand the use of these security features in a manner that is transparent to the developer (or the user). This can also allow the provided security to be distributed throughout the enterprise without a need for additional layering or translation of security processes.
In addition, such a framework can integrate the use of preexisting Java security SPI's 404 with custom SPI's 416,418. Additional SPI's such as, for example, a connection filter, an access decision interface, an audit channel, and a certificate authenticator, can be included or integrated with the security server. The security service mediates access to the entire range of secured enterprise resources.
Security Provider Interfaces
Security Provider Interfaces (SPI) that can be used with the invention include interfaces for:
It should be evident to one skilled in the art that the SPI's described herein are merely examples of the type of interface that can be used with the invention, and are listed here for purposes of illustrating the flexibility of the security service architecture provided by the invention. Other types of interface can be used to replace or augment those described, while remaining within the spirit and scope of the invention.
A JAAS Login Module that can be used with the invention can be based on the standard JAAS LoginModule, but can additionally support standard Login Module implementations. The authentication SPI can be extended to support management of users, groups, and to provide support for multiple JAAS Login Modules. Credentials can be shared across Login Module instances, and a separate Login Module to update with user profile information can be provided. The responsibilities of the Authentication SPI include authentication of users based on security realm scope, and the population of the principal in the JAAS Subject.
An Authorization SPI can provide for Access Decision, for which there is no Java equivalent sufficient. The Authorization SPI can support a variety of authorization models, both declarative and rules-based. A callback handler can be used to obtain access to invocation context. The SPI can also provide access to subject information, including principal identities, group membership and role assignments, and user profile information (optional). Multiple Access Decision providers can be configured in stack. The responsibilities of the Authorization SPI can include making authorization decision of permit, deny, or abstain, or access requests for protected resources scoped by application.
A Principal—>Role Mapping (JAAS LoginModule) SPI can be based on a JMS Login Module, and can be used to dynamically map roles to the identities of the principals contained in the Subject. The roles may have been explicitly defined by an administrator or from a deployment descriptor, or they may be dynamically computed based on the parameters fo the business request, the value of attributes in a principal's profile, as well as other conditions.
Principal—>Credential Mapping SPI
A Principal—>Credential Mapping (JAAS LoginModule) SPI can be based on the JAAS Login Module, and can be used to map principal identity when cross security domain policy or technology boundaries. The responsibilities of the Principal Mapping SPI is based on the Subject provided, and can be used to add public credentials with appropriate information to subject, such as password credential for username/password, and generic credential for token-type credentials.
Special care should be taken when migrating data between application server domains and different EIS instances, as application views defined against one EIS instance can contain identifiers and data specific to that instance. This can also be true of a connection factory used by the application view. A user may not be able to manually change instance-specific data in an application view or connection factory. These changes can, however, be made from an application view console by navigating to, and editing, the desired application view. The user can identify and update all EIS-specific data in the application view, as well as any events, services and associated connection factories.
Any references specific to an EIS instance can be replaced with references to a new EIS instance in the target environment. In particular, the user can edit the application view and connection factory definitions. Application view definitions may need changes in a parameter, such as “EventRouterURL” for example, that can be accessed through an application view “deploy” screen. This parameter can be used to refer to the event router in the target environment. Changes may also need to be made to parameters in the corresponding service definitions. These definitions can include adapter-specific data that refers to the EIS instance-specific data.
An editing feature can be used to change any EIS instance-specific parameters for the service. Event definition parameters may also need to be changed, which contain adapter-specific data that refers to the EIS-instance-specific data. Each adapter can place different properties into a service and event.
The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to one of ordinary skill in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5321841||Jan 29, 1993||Jun 14, 1994||Digital Equipment Corporation||System for determining the rights of object access for a server process by combining them with the rights of the client process|
|US5469562||Jun 26, 1992||Nov 21, 1995||Digital Equipment Corporation||Durable atomic storage update manager|
|US5604860||Oct 27, 1994||Feb 18, 1997||Xerox Corporation||Feature library and stored customized control interfaces|
|US5630131||Nov 14, 1994||May 13, 1997||Object Technology Licensing Corp.||Method and apparatus for importing and exporting archive files for a graphical user interface|
|US5748975||Jul 6, 1995||May 5, 1998||Sun Microsystems, Inc.||System and method for textual editing of structurally-represented computer programs with on-the-fly typographical display|
|US5801958||Sep 10, 1996||Sep 1, 1998||Lsi Logic Corporation||Method and system for creating and validating low level description of electronic design from higher level, behavior-oriented description, including interactive system for hierarchical display of control and dataflow information|
|US5835769||Sep 19, 1995||Nov 10, 1998||Sun Microsystems, Inc.||Apparatti and computer program products for integrating editors with applications|
|US5836014||May 16, 1994||Nov 10, 1998||Digital Equipment Corporation||Method of constructing a constant-folding mechanism in a multilanguage optimizing compiler|
|US5862327||Jun 10, 1996||Jan 19, 1999||Tactica Corporation||Activity based long-lived transaction system|
|US5867822||Jun 26, 1996||Feb 2, 1999||Sun Microsystems, Inc.||Method and apparatus for management of electronic calendars throughout an enterprise and management of events in a distributed system|
|US5933838||Apr 4, 1997||Aug 3, 1999||Microsoft Corporation||Database computer system with application recovery and recovery log sequence numbers to optimize recovery|
|US5944794||Oct 2, 1995||Aug 31, 1999||Kabushiki Kaisha Toshiba||User identification data management scheme for networking computer systems using wide area network|
|US5950010||Nov 25, 1996||Sep 7, 1999||J.D. Edwards World Source Co.||System and method for customized application package building and installation|
|US5961593||Jan 22, 1997||Oct 5, 1999||Lucent Technologies, Inc.||System and method for providing anonymous personalized browsing by a proxy system in a network|
|US5966535||Dec 7, 1995||Oct 12, 1999||At&T Corporation||Method and apparatus for generating program code for world wide web service applications|
|US6012083||Sep 24, 1996||Jan 4, 2000||Ricoh Company Ltd.||Method and apparatus for document processing using agents to process transactions created based on document content|
|US6016495||Sep 19, 1997||Jan 18, 2000||International Business Machines Corporation||Object-oriented framework mechanism for providing persistent storage|
|US6018730||Dec 22, 1998||Jan 25, 2000||Ac Properties B.V.||System, method and article of manufacture for a simulation engine with a help website and processing engine|
|US6023578||May 9, 1997||Feb 8, 2000||International Business Macines Corporation||Systems, methods and computer program products for generating an object oriented application for an object oriented environment|
|US6028997||May 30, 1997||Feb 22, 2000||International Business Machines Corporation||Method of generating an implementation of reusable parts from containers of a workflow process-model|
|US6029000||Dec 22, 1997||Feb 22, 2000||Texas Instruments Incorporated||Mobile communication system with cross compiler and cross linker|
|US6044217||Oct 23, 1997||Mar 28, 2000||International Business Machines Corporation||Hierarchical metadata store for an integrated development environment|
|US6067623 *||Nov 21, 1997||May 23, 2000||International Business Machines Corp.||System and method for secure web server gateway access using credential transform|
|US6070184||Aug 28, 1997||May 30, 2000||International Business Machines Corporation||Server-side asynchronous form management|
|US6085030||May 2, 1997||Jul 4, 2000||Novell, Inc.||Network component server|
|US6092102||Oct 24, 1997||Jul 18, 2000||University Of Pittsburgh Of The Commonwealth System Of Higher Education||System and method for notifying users about information or events of an enterprise|
|US6119149||Jun 5, 1998||Sep 12, 2000||I2 Technologies, Inc.||System and process allowing collaboration within and between enterprises for optimal decision making|
|US6125363||Mar 30, 1998||Sep 26, 2000||Buzzeo; Eugene||Distributed, multi-user, multi-threaded application development method|
|US6141686||Jun 23, 1998||Oct 31, 2000||Deterministic Networks, Inc.||Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control|
|US6141701||Mar 11, 1998||Oct 31, 2000||Whitney; Mark M.||System for, and method of, off-loading network transactions from a mainframe to an intelligent input/output device, including off-loading message queuing facilities|
|US6148336||Mar 13, 1998||Nov 14, 2000||Deterministic Networks, Inc.||Ordering of multiple plugin applications using extensible layered service provider with network traffic filtering|
|US6154738||May 21, 1999||Nov 28, 2000||Call; Charles Gainor||Methods and apparatus for disseminating product information via the internet using universal product codes|
|US6185734||Jul 21, 1998||Feb 6, 2001||Hewlett-Packard Company||Hierarchical registry structure for managing multiple versions of software components|
|US6189044||Oct 14, 1998||Feb 13, 2001||Hughes Electronics Corporation||Dynamic routing method for packet switched satellite communications|
|US6212546||Oct 1, 1998||Apr 3, 2001||Unisys Corporation||Providing a modular gateway architecture which isolates attributes of the client and server systems into independent components|
|US6222533||Aug 25, 1997||Apr 24, 2001||I2 Technologies, Inc.||System and process having a universal adapter framework and providing a global user interface and global messaging bus|
|US6226675||Oct 16, 1998||May 1, 2001||Commerce One, Inc.||Participant server which process documents for commerce in trading partner networks|
|US6226788||Jul 22, 1998||May 1, 2001||Cisco Technology, Inc.||Extensible network management system|
|US6230287||Sep 3, 1998||May 8, 2001||Mitel Corporation||Web based help desk|
|US6230309||Apr 25, 1997||May 8, 2001||Sterling Software, Inc||Method and system for assembling and utilizing components in component object systems|
|US6237135||Sep 11, 1998||May 22, 2001||Borland Software Corporation||Development system with visual design tools for creating and maintaining Java Beans components|
|US6243737||Apr 9, 1999||Jun 5, 2001||Translink Software, Inc.||Method and apparatus for providing direct transaction access to information residing on a host system|
|US6256676||Oct 5, 1999||Jul 3, 2001||Saga Software, Inc.||Agent-adapter architecture for use in enterprise application integration systems|
|US6269373||Feb 26, 1999||Jul 31, 2001||International Business Machines Corporation||Method and system for persisting beans as container-managed fields|
|US6282711||Aug 10, 1999||Aug 28, 2001||Hewlett-Packard Company||Method for more efficiently installing software components from a remote server source|
|US6292932||May 28, 1999||Sep 18, 2001||Unisys Corp.||System and method for converting from one modeling language to another|
|US6311327||Feb 12, 1999||Oct 30, 2001||Applied Microsystems Corp.||Method and apparatus for analyzing software in a language-independent manner|
|US6324681||Oct 1, 1998||Nov 27, 2001||Unisys Corporation||Automated development system for developing applications that interface with both distributed component object model (DCOM) and enterprise server environments|
|US6330569||Jun 30, 1999||Dec 11, 2001||Unisys Corp.||Method for versioning a UML model in a repository in accordance with an updated XML representation of the UML model|
|US6334114||Oct 31, 1997||Dec 25, 2001||Oracle Corporation||Method and apparatus for performing transactions in a stateless web environment which supports a declarative paradigm|
|US6336122||Oct 15, 1998||Jan 1, 2002||International Business Machines Corporation||Object oriented class archive file maker and method|
|US6338064||May 14, 1998||Jan 8, 2002||International Business Machines Corporation||Method for enabling a web server running a “closed” native operating system to impersonate a user of a web client to obtain a protected file|
|US6343265||Jul 28, 1998||Jan 29, 2002||International Business Machines Corporation||System and method for mapping a design model to a common repository with context preservation|
|US6345283||Jan 8, 1999||Feb 5, 2002||New Technologies Armor, Inc.||Method and apparatus for forensic analysis of information stored in computer-readable media|
|US6348970||Apr 29, 1998||Feb 19, 2002||Qwest Communications Int'l., Inc.||Apparatus and method for interfacing a computer network to a facsimile machine|
|US6349408||Jun 30, 1998||Feb 19, 2002||Sun Microsystems, Inc.||Techniques for implementing a framework for extensible applications|
|US6353923||Jan 30, 1998||Mar 5, 2002||Microsoft Corporation||Active debugging environment for debugging mixed-language scripting code|
|US6356906||Jul 26, 1999||Mar 12, 2002||Microsoft Corporation||Standard database queries within standard request-response protocols|
|US6360221||Sep 21, 1999||Mar 19, 2002||Neostar, Inc.||Method and apparatus for the production, delivery, and receipt of enhanced e-mail|
|US6360358||Mar 11, 1999||Mar 19, 2002||Microsoft Corporation||Maintenance of code knowledge for up-to-date access thereof|
|US6367068||Nov 13, 1998||Apr 2, 2002||Microsoft Corporation||Dynamic parsing|
|US6377939||May 4, 1999||Apr 23, 2002||Metratech||Pipelined method and apparatus for processing communication metering data|
|US6393605||Nov 17, 1999||May 21, 2002||Siebel Systems, Inc.||Apparatus and system for efficient delivery and deployment of an application|
|US6408311||Jun 30, 1999||Jun 18, 2002||Unisys Corp.||Method for identifying UML objects in a repository with objects in XML content|
|US6411698||Oct 13, 1998||Jun 25, 2002||Mci Communication Corporation||System and method for communication between a telephone data repository and downstream data processing applications|
|US6438594||Aug 31, 1999||Aug 20, 2002||Accenture Llp||Delivering service to a client via a locally addressable interface|
|US6445711||Apr 21, 2000||Sep 3, 2002||Sony Corporation||Method of and apparatus for implementing and sending an asynchronous control mechanism packet used to control bridge devices within a network of IEEE STD 1394 serial buses|
|US6463503||May 12, 1999||Oct 8, 2002||International Business Machines Corporation||Method and system for increasing concurrency during staging and destaging in a log structured array|
|US6470364||Feb 23, 1999||Oct 22, 2002||Sun Microsystems, Inc.||Method and apparatus for generating text components|
|US6516322||Apr 28, 2000||Feb 4, 2003||Microsoft Corporation||XML-based representation of mobile process calculi|
|US6549949||Aug 31, 1999||Apr 15, 2003||Accenture Llp||Fixed format stream in a communication services patterns environment|
|US6560769||Sep 28, 2000||May 6, 2003||Unisys Corporation||Computer-implemented method for generating a UML representation from JAVA source code|
|US6567738||Jan 30, 2001||May 20, 2003||Ford Global Technologies, Llc||Fueling control system|
|US6584454 *||Dec 31, 1999||Jun 24, 2003||Ge Medical Technology Services, Inc.||Method and apparatus for community management in remote system servicing|
|US6594693||Jan 22, 1999||Jul 15, 2003||Nitin A. Borwankar||Method and apparatus for a structured, synchronized conversation using electronic messages over a computer network|
|US6594700||Jun 14, 1999||Jul 15, 2003||International Business Machines Corporation||System and method for implementing a universal service broker interchange mechanism|
|US6601113||Jun 8, 1998||Jul 29, 2003||Telefonaktiebolaget Lm Ericsson (Publ)||System platform for a communication system|
|US6604198||May 3, 2002||Aug 5, 2003||Microsoft Corporation||Automatic object caller chain with declarative impersonation and transitive trust|
|US6609115 *||Dec 30, 1999||Aug 19, 2003||Ge Medical Systems||Method and apparatus for limited online access to restricted documentation|
|US6615258 *||Sep 24, 1998||Sep 2, 2003||Worldcom, Inc.||Integrated customer interface for web based data management|
|US6636491||Jan 11, 1999||Oct 21, 2003||Nokia Corporation||Access control method for a mobile communications system|
|US6637020||Dec 3, 1998||Oct 21, 2003||International Business Machines Corporation||Creating applications within data processing systems by combining program components dynamically|
|US6643652||Jan 12, 2001||Nov 4, 2003||Saba Software, Inc.||Method and apparatus for managing data exchange among systems in a network|
|US6654932||Oct 29, 1999||Nov 25, 2003||International Business Machines Corporation||Validating data within container objects handled by view controllers|
|US6662357||Aug 31, 1999||Dec 9, 2003||Accenture Llp||Managing information in an integrated development architecture framework|
|US6678518||Dec 9, 1999||Jan 13, 2004||Nokia Corporation||Dynamic content filter in a gateway|
|US6684388||Aug 22, 2000||Jan 27, 2004||International Business Machines Corporation||Method for generating platform independent, language specific computer code|
|US6687702||Sep 25, 2001||Feb 3, 2004||Sybass, Inc.||Methodology providing high-speed shared memory access between database middle tier and database server|
|US6687848||Oct 30, 2000||Feb 3, 2004||Sun Microsystems, Inc.||Techniques for preventing information loss in a business to business message in an enterprise computer system|
|US6721740||Jun 5, 1998||Apr 13, 2004||Sun Microsystems, Inc.||Method and apparatus of performing active update notification|
|US6721779||Jul 7, 2000||Apr 13, 2004||Softwired Ag||Messaging proxy system|
|US6732237||Aug 29, 2000||May 4, 2004||Oracle International Corporation||Multi-tier caching system|
|US6738975||Oct 5, 1999||May 18, 2004||Software Ag, Inc.||Extensible distributed enterprise application integration system|
|US6748420||Oct 11, 2000||Jun 8, 2004||Cisco Technology, Inc.||Methods and apparatus for providing shared access to an application|
|US6754884||Jul 2, 2001||Jun 22, 2004||Bea Systems, Inc.||Programming language extensions for processing XML objects and related applications|
|US6757689||Sep 7, 2001||Jun 29, 2004||Hewlett-Packard Development Company, L.P.||Enabling a zero latency enterprise|
|US6789054||Apr 25, 1999||Sep 7, 2004||Mahmoud A. Makhlouf||Geometric display tools and methods for the visual specification, design automation, and control of adaptive real systems|
|US6795967||Jan 26, 1999||Sep 21, 2004||Microsoft Corporation||Changing user identities without closing applications|
|US6799718||Jul 10, 2002||Oct 5, 2004||Borland Software Corp.||Development assistance for mixed-language sources|
|US6802000||Oct 28, 1999||Oct 5, 2004||Xerox Corporation||System for authenticating access to online content referenced in hardcopy documents|
|US6804686||Sep 10, 2002||Oct 12, 2004||Borland Software Corporation||System and methodology for providing fixed UML layout for an object oriented class browser|
|US6823495||Sep 14, 2000||Nov 23, 2004||Microsoft Corporation||Mapping tool graphical user interface|
|US6832238||May 24, 2000||Dec 14, 2004||Sun Microsystems, Inc.||Local transaction management|
|US6957199 *||Jun 5, 2001||Oct 18, 2005||Douglas Fisher||Method, system and service for conducting authenticated business transactions|
|US6959336 *||Apr 7, 2001||Oct 25, 2005||Secure Data In Motion, Inc.||Method and system of federated authentication service for interacting between agent and client and communicating with other components of the system to choose an appropriate mechanism for the subject from among the plurality of authentication mechanisms wherein the subject is selected from humans, client applications and applets|
|US6981043 *||Mar 27, 2001||Dec 27, 2005||International Business Machines Corporation||Apparatus and method for managing multiple user identities on a networked computer system|
|US6999912 *||Mar 13, 2001||Feb 14, 2006||Microsoft Corporation||Provisioning computing services via an on-line networked computing environment|
|US20020029269 *||Jun 29, 2001||Mar 7, 2002||Campus Pipeline, Inc.||Methods and systems for coordinating the termination of sessions on one or more systems|
|US20030014656 *||Jun 29, 2001||Jan 16, 2003||International Business Machines Corporation||User registry adapter framework|
|1||"Introducing Microsoft DotNet"; by ChristopheLauer, Jul. 2, 2002; http://web.archive.org/web/20020702162429/http://www.freevbcode.com/ShowCode.asp?ID=2171; pp. 1-10.|
|2||Allamaraju, et al., Professional Java Server Programming J2EE 1.3 Edition, Sep. 2001, 24 pages.|
|3||Alonso et al., "Advanced Transaction Models in Workflow Contexts", IEEE, Feb. 1996, Proceedings of 12th International Conference on Data Engineering, retrieved from: http://citeseer.ist.psu.edualonso96advanced.html., pp. 574-581.|
|4||Altova, "XML-to-XML Mapping", 2007, 3 pages, Altova Map Force.|
|5||BEA Systems, Inc., "Transforming Data Using Xquery Mapper", BEA AquaLogic Service Bus 2.0 Documentation, 2006, 19 pages.|
|6||Blake, Ruled-Driven Coordination Agent: "A Self-Configureable Agent Architecture for Distributed Control"; IEEE Mar. 2001, pp. 271-277.|
|7||Bogunovic, "A Programming Model for Composing Data Flow Collaborative Applications", Proceedings of the IEEE International Conference on Engineering of Computer Based Systems, Mar. 7-12, 1999, pp. 106-112.|
|8||C. Moran et al. "ARIES: A Transaction Recovery Method Supporting Fine-Granularity Locking and Partial Rollbacks Using Write-Ahead Logging", ACM Transaction on Database Systems, vol. 17, No. 1, Mar. 1992, pp. 94-162.|
|9||Chen et al., "eCo Architecture for Electronic Commerce Interoperability", Jun. 29, 1999, CommerceNet, pp. 1-107.|
|10||Dahalin et al., Workflow Interoperability Using Extensible Markup Language (XML), IEEE, Jul. 2002, pp. 513-516.|
|11||Ed Roman & Rickard Öberg, The Technical Benefits of EJB and J2EE Technologies over COM+ and Windows DNA, Enterprise Edition (J2EE) Technologies, Dec. 1999, pp. 1-24.|
|12||Embury et al., "Assisting the Comprehension of Legacy Transaction", Reverse Engineering, 2001, Proceedings, Eighth Working Conference on Oct. 2-5, 2001, pp. 345-354.|
|13||Enrique Duvos & Azer Bestavros, An Infrastructure for the Dynamic Distribution of Web Application and Services, Department of Computer Science Boston University, Dec. 2000, pp. 1-22.|
|14||Erich Liebmann et al., "Adaptive Data Dissemination and Caching for Edge Service Architectures Built wi the J2EE", Mar. 2004, ACM Press ACM Symposium on Applied Computer, pp. 1717-1724.|
|15||European Search Report Dated Aug. 8, 2007 in connection with Application No. 02784131.1, 4 pages.|
|16||FOLDOC, "Definition of JMS", "http://foldoc.prg/?JMS", Jun. 6, 2001, 1 page.|
|17||HP, "HP Application Server Developer's Guide," Version 8.0, Hewlett-Packard Company, 1999-2001, pp. 27-81, 127-160, 195-271.|
|18||Jamper, "Jamper-Java XML Mapper", 2007, 4 pages, Sourceforge.|
|19||JAVA(TM) Debug Interface, definitions, retrieved from <URL http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdi/overview-summary.html, Feb. 21, 2007.|
|20||Kilgore, "Multi-Language, Open-Source Modeling Using the Microsoft Architecture", Simulation Conference, 2002, Proceedings of the Winter, Dec. 8-11, 2002, vol. 1, pp. 629-633.|
|21||Kunisetty "Workflow Modeling and simulation Using an Extensible Object-Oriented Knowledge Base Management System" Citeseer, 1996, pp. 1-60.|
|22||Marcello Mariucci, Enterprise Application Server Development Environments, University of Stuttgart, Oct. 10, 2000, pp. 1-30.|
|23||Mays et al., "A Persistent Store for Large Shared Knowledge Bases", Knowledge and Data Engineering, IEEE Transactions on vol. 3, Issue 1, Mar. 1991, pp. 33-41.|
|24||Microsoft, "Microsoft.net Framework", 2001, Microsoft Corporation, 54 pages.|
|25||Muller, "Event-Oriented Dynamic Adaptation of Workflows: Model, Architecture, and Implementation", 2002, University of Leipzig, Germany, 351 pages.|
|26||Newcomer, Eric, "Understanding Web Services: XML, WSDL, SOAP, and UDDI", May 2002, 100 pages.|
|27||Ort, et al. "Java Architecture for XML Binding (JAXB)", Mar. 2003, Java-Sun, 14 pages.|
|28||Paul, Laura Gibbone, "RosettaNet: Teaching business to work together", Oct. 1, 1999. http://www.developer.com/xml/article.php/616641.|
|29||*||Pekka Sjoberg; The Java Message Service 1.0.2; 2001.|
|30||Peltz, "Web Service Orchestration", HP, Jan. 2003, Hewlett Packard, Co., 20 pages.|
|31||Plaindoux, "XML transducers in Java", May 2002, The Eleventh International World Wide Conference, retrieved from: http://www2002.org/CDROM/poster/132/index.html., 6 pages.|
|32||Smith, et al. "Marching Towards a Software Reuse Future", ACM Ada Letters, Nov./Dec. 1994, pp. 62-72 vol. 14, No. 6.|
|33||Sosnoski, "XML and Java Technologies: Data Binding, Part 1: Code Generation Approaches-JAXB and more", IBM, pp. 1-11, 2003.|
|34||Stylus Studio, "Xquery Mapper", 2007, 6 pages, Stylus Studios.|
|35||Sun Microsystems, "J2EE Connector Architecture 1.0", Aug. 2001, 90 pages.|
|36||Sun Microsystems, IPlanet Application Server 6.0 White Paper, iPlanet E-Commerce Solutions, May 25, 2000, pp. 1-104.|
|37||Sun Microsystems, 'Java Message Service Version 1.0.2b, Aug. 27, 2001, 118 pages.|
|38||Sung et al. , "A Multimedia Authoring Tool for the Internet", IEEE Transactions on Consumer Electronics, 1997. pp. 304-308.|
|39||Tang et al., "Integrating Remote Invocation and Distributed Shared State", Parallel and Distributed Processing Symposium, 2004, Proceedings, 18th International, Apr. 26-30, 2004, (10 pages).|
|40||U.S. Appl. No. 10/271,047, filed Oct. 15, 2002, Mitch Upton.|
|41||U.S. Appl. No. 10/271,156, filed Oct. 15, 2002, Mitch Upton.|
|42||U.S. Appl. No. 10/271,157, filed Oct. 15, 2002, Mitch Upton.|
|43||U.S. Appl. No. 10/271,162, filed Oct. 15, 2002, Mitch Upton.|
|44||U.S. Appl. No. 10/271,194, filed Oct. 15, 2002, Mitch Upton.|
|45||U.S. Appl. No. 10/271,244, filed Oct. 15, 2002, Mitch Upton.|
|46||U.S. Appl. No. 10/271,402, filed Oct. 15, 2002, Mitch Upton.|
|47||U.S. Appl. No. 10/271,410, filed Oct. 15, 2002, Mitch Upton.|
|48||U.S. Appl. NO. 10/271,414, filed Oct. 15, 2002, Mitch Upton.|
|49||U.S. Appl. No. 10/271,423, filed Oct. 15, 2002, Mitch Upton.|
|50||Van Der Aalst et al., "Verification of XRL: An XML-based Workflow Language", IEEE, Jul. 2001, The Sixth International Conference on Computer Supported Cooperative Work in Design, pp. 427-432.|
|51||Van Der Aalst et al., Verification of XRL: An XML-Based Workflow Language, IEEE, Jul. 2001, pas. 427-432.|
|52||Wikipedia, Java Architecture for XML Binding (JAXB), Oct. 2007, 3 pages.|
|53||Wilink, Metal-Compilation for C++, Jan. 2000, University of Surrey, 379 pages.|
|54||XA Resource (Java 2 Platform EE v1.4), "Interface XAResource", Dec. 12, 2002, 9 pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7886038||May 27, 2008||Feb 8, 2011||Red Hat, Inc.||Methods and systems for user identity management in cloud-based networks|
|US8108912||May 29, 2008||Jan 31, 2012||Red Hat, Inc.||Systems and methods for management of secure data in cloud-based network|
|US8239509||May 28, 2008||Aug 7, 2012||Red Hat, Inc.||Systems and methods for management of virtual appliances in cloud-based network|
|US8255529||Feb 26, 2010||Aug 28, 2012||Red Hat, Inc.||Methods and systems for providing deployment architectures in cloud computing environments|
|US8271653||Aug 31, 2009||Sep 18, 2012||Red Hat, Inc.||Methods and systems for cloud management using multiple cloud management schemes to allow communication between independently controlled clouds|
|US8301887 *||Oct 30, 2012||Blue Coat Systems, Inc.||Method and system for automated authentication of a device to a management node of a computer network|
|US8316125||Aug 31, 2009||Nov 20, 2012||Red Hat, Inc.||Methods and systems for automated migration of cloud processes to external clouds|
|US8341625||May 29, 2008||Dec 25, 2012||Red Hat, Inc.||Systems and methods for identification and management of cloud-based virtual machines|
|US8364819||May 28, 2010||Jan 29, 2013||Red Hat, Inc.||Systems and methods for cross-vendor mapping service in cloud networks|
|US8375223||Oct 30, 2009||Feb 12, 2013||Red Hat, Inc.||Systems and methods for secure distributed storage|
|US8402139||Feb 26, 2010||Mar 19, 2013||Red Hat, Inc.||Methods and systems for matching resource requests with cloud computing environments|
|US8458658||Feb 29, 2008||Jun 4, 2013||Red Hat, Inc.||Methods and systems for dynamically building a software appliance|
|US8504443||Aug 31, 2009||Aug 6, 2013||Red Hat, Inc.||Methods and systems for pricing software infrastructure for a cloud computing environment|
|US8504689||May 28, 2010||Aug 6, 2013||Red Hat, Inc.||Methods and systems for cloud deployment analysis featuring relative cloud resource importance|
|US8606667||Feb 26, 2010||Dec 10, 2013||Red Hat, Inc.||Systems and methods for managing a software subscription in a cloud network|
|US8606897||May 28, 2010||Dec 10, 2013||Red Hat, Inc.||Systems and methods for exporting usage history data as input to a management platform of a target cloud-based network|
|US8612566||Jul 20, 2012||Dec 17, 2013||Red Hat, Inc.||Systems and methods for management of virtual appliances in cloud-based network|
|US8612577||Nov 23, 2010||Dec 17, 2013||Red Hat, Inc.||Systems and methods for migrating software modules into one or more clouds|
|US8612615||Nov 23, 2010||Dec 17, 2013||Red Hat, Inc.||Systems and methods for identifying usage histories for producing optimized cloud utilization|
|US8631099||May 27, 2011||Jan 14, 2014||Red Hat, Inc.||Systems and methods for cloud deployment engine for selective workload migration or federation based on workload conditions|
|US8639950||Dec 22, 2011||Jan 28, 2014||Red Hat, Inc.||Systems and methods for management of secure data in cloud-based network|
|US8713147||Nov 24, 2010||Apr 29, 2014||Red Hat, Inc.||Matching a usage history to a new cloud|
|US8769083||Aug 31, 2009||Jul 1, 2014||Red Hat, Inc.||Metering software infrastructure in a cloud computing environment|
|US8782192||May 31, 2011||Jul 15, 2014||Red Hat, Inc.||Detecting resource consumption events over sliding intervals in cloud-based network|
|US8782233 *||Nov 26, 2008||Jul 15, 2014||Red Hat, Inc.||Embedding a cloud-based resource request in a specification language wrapper|
|US8825791||Nov 24, 2010||Sep 2, 2014||Red Hat, Inc.||Managing subscribed resource in cloud network using variable or instantaneous consumption tracking periods|
|US8832219||Mar 1, 2011||Sep 9, 2014||Red Hat, Inc.||Generating optimized resource consumption periods for multiple users on combined basis|
|US8832459||Aug 28, 2009||Sep 9, 2014||Red Hat, Inc.||Securely terminating processes in a cloud computing environment|
|US8849971||May 28, 2008||Sep 30, 2014||Red Hat, Inc.||Load balancing in cloud-based networks|
|US8862720||Aug 31, 2009||Oct 14, 2014||Red Hat, Inc.||Flexible cloud management including external clouds|
|US8904005||Nov 23, 2010||Dec 2, 2014||Red Hat, Inc.||Indentifying service dependencies in a cloud deployment|
|US8909783||May 28, 2010||Dec 9, 2014||Red Hat, Inc.||Managing multi-level service level agreements in cloud-based network|
|US8909784||Nov 30, 2010||Dec 9, 2014||Red Hat, Inc.||Migrating subscribed services from a set of clouds to a second set of clouds|
|US8924539||Nov 24, 2010||Dec 30, 2014||Red Hat, Inc.||Combinatorial optimization of multiple resources across a set of cloud-based networks|
|US8935692||May 22, 2008||Jan 13, 2015||Red Hat, Inc.||Self-management of virtual machines in cloud-based networks|
|US8943497||May 29, 2008||Jan 27, 2015||Red Hat, Inc.||Managing subscriptions for cloud-based virtual machines|
|US8949426||Nov 24, 2010||Feb 3, 2015||Red Hat, Inc.||Aggregation of marginal subscription offsets in set of multiple host clouds|
|US8954564||May 28, 2010||Feb 10, 2015||Red Hat, Inc.||Cross-cloud vendor mapping service in cloud marketplace|
|US8959221||Mar 1, 2011||Feb 17, 2015||Red Hat, Inc.||Metering cloud resource consumption using multiple hierarchical subscription periods|
|US8977750||Feb 24, 2009||Mar 10, 2015||Red Hat, Inc.||Extending security platforms to cloud-based networks|
|US8984104||May 31, 2011||Mar 17, 2015||Red Hat, Inc.||Self-moving operating system installation in cloud-based network|
|US8984505||Nov 26, 2008||Mar 17, 2015||Red Hat, Inc.||Providing access control to user-controlled resources in a cloud computing environment|
|US9037692||Nov 26, 2008||May 19, 2015||Red Hat, Inc.||Multiple cloud marketplace aggregation|
|US9037723||May 31, 2011||May 19, 2015||Red Hat, Inc.||Triggering workload movement based on policy stack having multiple selectable inputs|
|US9053472||Feb 26, 2010||Jun 9, 2015||Red Hat, Inc.||Offering additional license terms during conversion of standard software licenses for use in cloud computing environments|
|US9092243||May 28, 2008||Jul 28, 2015||Red Hat, Inc.||Managing a software appliance|
|US9100311||Jun 2, 2014||Aug 4, 2015||Red Hat, Inc.||Metering software infrastructure in a cloud computing environment|
|US9104407||May 28, 2009||Aug 11, 2015||Red Hat, Inc.||Flexible cloud management with power management support|
|US9112836||Jan 14, 2014||Aug 18, 2015||Red Hat, Inc.||Management of secure data in cloud-based network|
|US20080307498 *||Dec 27, 2007||Dec 11, 2008||Waterstone Environmental Hydrology & Engineering, Inc.||Access control for server-based geographic information system|
|US20090256450 *||Dec 3, 2008||Oct 15, 2009||Claude Chevrette||Tire actuated generator for use on cars|
|US20090293056 *||Nov 26, 2009||James Michael Ferris||Methods and systems for automatic self-management of virtual machines in cloud-based networks|
|US20100057831 *||Aug 28, 2008||Mar 4, 2010||Eric Williamson||Systems and methods for promotion of calculations to cloud-based computation resources|
|US20100131324 *||Nov 26, 2008||May 27, 2010||James Michael Ferris||Systems and methods for service level backup using re-cloud network|
|US20100131649 *||Nov 26, 2008||May 27, 2010||James Michael Ferris||Systems and methods for embedding a cloud-based resource request in a specification language wrapper|
|US20100131948 *||Nov 26, 2008||May 27, 2010||James Michael Ferris||Methods and systems for providing on-demand cloud computing environments|
|US20100131949 *||Nov 26, 2008||May 27, 2010||James Michael Ferris||Methods and systems for providing access control to user-controlled resources in a cloud computing environment|
|US20100132016 *||Nov 26, 2008||May 27, 2010||James Michael Ferris||Methods and systems for securing appliances for use in a cloud computing environment|
|U.S. Classification||713/170, 726/4|
|International Classification||G06F7/00, G06F9/00, G06F15/16, G09G5/00, G06F9/46, G06F9/54, G06F15/163, G06F7/04, H04L9/00|
|Cooperative Classification||Y10S707/99943, Y10S707/99945, G06F9/542, G06F9/541, G06Q10/103, G06F2209/544|
|European Classification||G06F9/54A, G06F9/54B, G06Q10/103|
|Jan 21, 2003||AS||Assignment|
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UPTON, MITCH;REEL/FRAME:013685/0470
Effective date: 20030105
|Feb 15, 2003||AS||Assignment|
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UPTON, MITCH;REEL/FRAME:013780/0767
Effective date: 20030105
|Jun 1, 2010||CC||Certificate of correction|
|Oct 15, 2010||AS||Assignment|
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025192/0244
Effective date: 20101008
|Nov 7, 2012||FPAY||Fee payment|
Year of fee payment: 4