US20070157297A1 - System and method for server security and entitlement processing - Google Patents
System and method for server security and entitlement processing Download PDFInfo
- Publication number
- US20070157297A1 US20070157297A1 US11/686,218 US68621807A US2007157297A1 US 20070157297 A1 US20070157297 A1 US 20070157297A1 US 68621807 A US68621807 A US 68621807A US 2007157297 A1 US2007157297 A1 US 2007157297A1
- Authority
- US
- United States
- Prior art keywords
- security
- access
- server
- authorization
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000012545 processing Methods 0.000 title description 6
- 230000008569 process Effects 0.000 abstract description 23
- 238000013475 authorization Methods 0.000 description 69
- 230000007246 mechanism Effects 0.000 description 43
- 238000013507 mapping Methods 0.000 description 10
- 238000012550 audit Methods 0.000 description 7
- 238000011156 evaluation Methods 0.000 description 7
- 230000014509 gene expression Effects 0.000 description 7
- 230000010354 integration Effects 0.000 description 6
- 238000012546 transfer Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 235000006719 Cassia obtusifolia Nutrition 0.000 description 4
- 235000014552 Cassia tora Nutrition 0.000 description 4
- 244000201986 Cassia tora Species 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- VBMOHECZZWVLFJ-GXTUVTBFSA-N (2s)-2-[[(2s)-6-amino-2-[[(2s)-6-amino-2-[[(2s,3r)-2-[[(2s,3r)-2-[[(2s)-6-amino-2-[[(2s)-2-[[(2s)-6-amino-2-[[(2s)-2-[[(2s)-2-[[(2s)-2,6-diaminohexanoyl]amino]-5-(diaminomethylideneamino)pentanoyl]amino]propanoyl]amino]hexanoyl]amino]propanoyl]amino]hexan Chemical compound NC(N)=NCCC[C@@H](C(O)=O)NC(=O)[C@H](CCCCN)NC(=O)[C@H](CCCCN)NC(=O)[C@H]([C@@H](C)O)NC(=O)[C@H]([C@H](O)C)NC(=O)[C@H](CCCCN)NC(=O)[C@H](C)NC(=O)[C@H](CCCCN)NC(=O)[C@H](C)NC(=O)[C@H](CCCN=C(N)N)NC(=O)[C@@H](N)CCCCN VBMOHECZZWVLFJ-GXTUVTBFSA-N 0.000 description 3
- 238000013459 approach Methods 0.000 description 3
- 108010068904 lysyl-arginyl-alanyl-lysyl-alanyl-lysyl-threonyl-threonyl-lysyl-lysyl-arginine Proteins 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 244000035744 Hura crepitans Species 0.000 description 1
- 244000046052 Phaseolus vulgaris Species 0.000 description 1
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000001186 cumulative effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000010561 standard procedure Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2145—Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
Definitions
- the invention is related generally to server security mechanisms, and specifically to an architecture for server security.
- FIG. 1 shows a typical example of a security mechanism commonly used today.
- Clients 102 , 104 access a secured resource such as an application server 106 via a number of protocols; including for example http (hypertext transfer protocol) 110 and IIOP (Internet Inter-ORB protocol) 112 .
- the access requests are filtered through a security layer 108 which determines, typically based on a set of hardwired rules, whether to allow or disallow the requested access.
- the security layer may be a component of the protected resource (eg. the application server itself) or may operate as a separate entity (for example as part of a firewall system or device).
- security is often thought of as a simple “permit or deny” mechanism, designed in such a way as to understand the protected resources provided by the server, and to adhere to a predefined set of rules governing a user's or a client's access rights to those resources.
- security mechanism does not lend itself to easy modification of the rules to reflect new changes in business policy regarding security.
- Role-based access control is becoming one of the primary form of authorization requested by customers and system integrators.
- the trend in use of roles allows organizational identity to be used as an abstract form of identity when making authorization decisions.
- the use of roles provides a mechanism to reduce both the cost and errors in the administration of application security since it simplifies the amount of administration.
- Java 2 Enterprise Edition defines a declarative form of role-based access control. However, because it is based on a declarative scheme, the association of roles to principals is static. In addition, the current Java 2 Enterprise Edition specification provides no means by which the context of a business request, such as the parameters of the request or the identity of the target, can be taken into account when determining the roles to be associated with a given principal. Consequently, application developers are required to implement business policy rules within the application to compute dynamic roles associations in order to support concepts like “owner”.
- the foundation of the requirements for this richer level of authorization can be found in the intersection of classical authorization mechanisms, such as Access Control Lists, and business policy enforcement; and include the ability to take the context of the business request into consideration when making an authorization decision.
- the request context may include the identity of the target object, the value of the parameter of the request, and potentially environmental information such as the network or IP address of the initiating client.
- the Service Provider Interface is the mechanism used by several application servers, including the WebLogic Server product from BEA Systems, Inc., San Jose, Calif., to allow integration with external authorization providers.
- This SPI realm has a number of limitations that limit it's ability to be used as a successful means to integrate 3rd-party authorization mechanisms, or new authorization capabilities being required by customers and system integrators.
- the second limitation of the current realm SPI is point of enforcement.
- the current realm mechanism does not allow the point at which the decision is made to allow access to a protected resource to exist within the realm itself. Instead, the point of enforcement is within the application server itself. Because of this approach, the current realm is defined to support only a permission-based authorization mechanism where the realm simply acts as a database of Access Control Lists.
- the complexities of providing a Java 2 Policy object that can also support the Java 2 sandbox rules is unacceptable to most vendors.
- enforcement Mechanism Support of the current realm SPI As with the point of enforcement, the enforcement mechanisms allowed by the current realm SPI are limited to those based on permission-based authorization mechanisms. This is counter to the capabilities of the leading 3rd-party authorization providers, the integration of which is being requested by customers and systems integrators on a daily basis.
- JAVA, JAVA TWO ENTERPRISE EDITION (J2EE), and ENTERPRISE JAVABEANS (EJB) are trademarks of Sun Microsystems, Inc.
- WEBLOGIC is a trademark of BEA Systems, Inc.
- the invention is related generally to server security mechanisms, and specifically to an architecture that provides for server security and entitlement processing.
- a pluggable architecture allows security and business logic plugins to be inserted into a security service hosted by a server, and to control access to one or more secured resources on that server, on another server within the security domain, or between security domains.
- the security service may act as a focal point for security enforcement, and access rights determination, and information used or determined within one login process can flow transparently and automatically to other login processes.
- the invention also introduces the concept of entitlements that are used within an access context.
- a “user” or a “client” may refer to the same thing—either a physical person, a hardware device or software application under control of the physical person, or a hardware device or software application operating under autonomous control without user intervention.
- the user (or client) is the entity which is trying 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 etc.
- the security service may determine the type of access request, the destination (protected resource), and the setting in which the request is made—hereinafter referred to as the access context or simply the context. From this information the security service can determine an “entitlement”, or a set of entitlements, for the user. Entitlements clearly denote what a particular user may or may not do with a particular resource, in a particular context. Entitlements reflect not only the technical aspects of the secure environment (the permit or deny concept), but can be used to represent the business logic or functionality required by the server provider. In this way entitlements bridge the gap between a simple security platform, and a complex business policy platform.
- the invention comprises a security system for allowing a client to access a protected resource, comprising an application interface mechanism for receiving an access request from a client application to access a protected resource, and communicating said access request to a security service; a security service for making a decision to permit or deny said access request; and a resource interface for communicating permitted access requests to said protected resource.
- the invention comprises a method of allowing a client to access a protected resource, comprising receiving at an application interface mechanism an access request from a client application to access a protected resource and communicating said access request to a security service; making a decision at said security service to permit or deny said access request; and communicating via a resource interface a permitted access request to said protected resource.
- FIG. 1 shows an illustration of a client/server architecture in accordance with the prior art.
- FIG. 2 shows an illustration of a client/server architecture in accordance with the invention.
- FIG. 3 shows an illustration of a security service in accordance with the invention.
- FIG. 4 shows a flowchart of a method used by the security service in accordance with the invention.
- FIG. 5 shows an illustration of a server security deployment tool and process in accordance with the invention.
- FIG. 6 shows a flowchart of a method used by the server security deployment tool in accordance with the invention.
- FIG. 7 shows an illustration of a security service and a protected resource in accordance with the invention.
- FIG. 8 shows a flowchart of a method used by the security service to allow access to a protected resource in accordance with the invention.
- FIG. 9 shows an illustration of a security layer in accordance with an embodiment of the invention.
- FIG. 10 shows an illustration of an entitlement mechanism in accordance with an embodiment of the invention.
- FIG. 11 shows an illustration of a login across several security domain models in accordance with the invention.
- An embodiment of the invention includes a security architecture that provides for server security and entitlement processing, that allows security and business logic plugins to be inserted into a security service hosted by a server, and that can 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 acts 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.
- Embodiments of the invention described herein allow for the determination of entitlements as used within an access context.
- a user is trying 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 resource may be used while remaining within the spirit and scope of the invention.
- the security service determines 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 clearly denote what a particular user may do 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.
- J2EE Java 2 Enterprise Edition
- CSI Common Secure Interoperability
- SAS Stateless Authentication Service
- CSI Common Secure Interoperability
- SAS Stateless Authentication Service
- Another important goal of the invention is 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.
- TLS Transport Level Security
- a security realm or domain can span a single server, a plurality of servers, a cluster of servers, or a management domain.
- the invention allows for administrative control of identity propagation within, across, and between security domains.
- the identity of a client application or user can be propagated and scoped by the security domain. For example:
- the initiating identity can be represented as being anonymous. For example:
- the security architecture or framework provided by the invention is intended to address the requirements put forth and many other things. Focusing exclusively on the authorization requirements, the security architecture attempts to provide the following capabilities in addition to a typical permission-based authorization:
- Dynamic Role Association is a mechanism to allow a late binding of the association of roles to principals, that 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 occurs 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.
- 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 is typically utilized as values of parameters in an expression that is to be evaluated by a rules or expression evaluation engine.
- a rules or expression 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 ofmiles flown by the principal, that are then used as parameter of the expression.
- this same functionality is also responsible for associating any roles that were statically defined either through the consumption of a J2EE defined Deployment Descriptor or by an administrator.
- 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 are then available to any authorization decisions on protected resources, as well as business container and application code.
- 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 allows an authorization decision about a protected resource to be determined that is potentially based on the context of the request.
- the scope of enforcement has been broadened to apply to all execution and resource containers. This is accomplished by having all execution and resource containers obtain authorization and role mapping services through an AccessController object provided by a Security Service.
- the AccessController utilizes the authorization services provided through the Service Provider Interfaces in order to provide the requested capabilities.
- the Service Provider Interfaces that actually define the mechanisms used to provide Dynamic Role Association and Parametric Authorization are 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.
- the methods defined on the Service Provider Interfaces that comprise the authorization framework 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 allows the delegated authorization approach to support both capabilities-based as well as permission-based implementations.
- the authorization decision is made using the context of the request, therefore the authorization decision more closely represent real business decisions. There is very little need for compensating security checks in the application itself. For example, using the invention 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.
- the 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).
- JAAS Java Authentication and Authorization Service
- the provider is capable of requesting specific context information be returned.
- the container's callback handler is called, the container responds 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.
- the application, nor the container is 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 implementation should be able to specify 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 should be able to 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 should be in the form of a callback similar to that defined for JAAS.
- the implementation might callback for each piece of information individually, request multiple pieces of information in a single callback, or a combination of both.
- An implementation should be able to 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.
- 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 should result in a boolean value that indicates whether the rule was successfully satisfied or not.
- the invention provides enterprise application developers with a framework architecture within which application implementations, particularly login, authorization, and auditing implementations, may 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.
- the framework architecture provided by the invention particularly allows Java developers to make use of existing Java security features, but to greatly expand the use of these security features in a manner that is transparent to the developer (or the user), and that can allow the security provided to be distributed throughout the enterprise without a need for additional layering or translation of security processes.
- Embodiments of the invention are particularly useful in the field of enterprise and server security and business workflow. Since the framework uses a pluggable architecture, it allows third-party vendors to provide security implementation plug-ins without a need for the core architecture to be modified. These plug-ins may include tools for digital certificate and key retrieval, certificate validation, and revocation mechanisms (e.g. CRL and OCSP).
- the pluggable framework architecture thus allows for the secure access control of enterprise resources, such as enterprise Java beans (EJB's), applications (including servlets and JSP's), and other networked resources (such as RMI, JNDI, and JMS destinations).
- enterprise resources such as enterprise Java beans (EJB's), applications (including servlets and JSP's), and other networked resources (such as RMI, JNDI, and JMS destinations).
- EJB's enterprise Java beans
- applications including servlets and JSP's
- other networked resources such as RMI, JNDI, and JMS destinations.
- the framework architecture of the invention is especially suited to providing amethod of secure authorization and secure resource access throughout an enterprise-wide security domain.
- Each server with a domain may provide a different set of features, services and applications.
- the invention allows developers to deploy client applications which can make use of each server's particular services through a single sign-on mechanism that determines the client's access privileges throughout the domain or between cooperating domains.
- FIG. 2 shows an example of a security architecture in accordance with an embodiment of the invention.
- clients 202 , 204 may attempt to access a secured service or resource 206 , such as a persistent directory server, via a transaction or application server 208 .
- a transaction server is the Weblogic Server product from BEA Systems Inc., San Jose, Calif., although the invention may be used with any other server product or equivalent system.
- Internet CORBA clients will typically attempt to make such an access through an Internet Inter-ORB Protocol (IIOP) request 212 .
- IIOP Internet Inter-ORB Protocol
- Web clients will typically attempt to make an access through a series of hypertext transfer protocol (http) requests 210 , either directly via a Web server 214 , or via a proxy plug-in 216 (in which case the proxy may also provide additional functionality, such as, for example, secure socket layer (SSL) encryption 218 ).
- https hypertext transfer protocol
- the connection attempt is received by the transaction server, often via an initial connection filter 220 , and is passed to the security service 222 .
- the security service 222 is the focal point for security determination, including client and user level resource access, authorization, certification, privilege assessment and entitlement determination.
- EJB's 224 Enterprise Java Beans
- Web applications WebApp's
- other forms of applications may all use the security service through the use of containers.
- the security service handles calls from these containers to the protected resource, which in the case of FIG. 2 .
- the calls may be handled by, for example, a plurality of managed beans (MBeans) 230 , or the Java Named Directory Interface (JNDI) 232 .
- Means managed beans
- JNDI Java Named Directory Interface
- FIG. 3 illustrates an embodiment of the security service architecture 300 in greater detail.
- the security service augments the basic security services and features provided by the standard Java2 Enterprise Edition security set.
- the basic Java security set 302 includes security provider interfaces 304 for key storage, authentication, certificate validation, and secure sockets, among others.
- Customer applications 306 may be written to directly take advantage of the Java security layer and these SPI's .
- the invention as shown in FIG. 3 greatly enhances the developer's options in making use of these and other security features.
- customer applications are deployed in containers, for example, an EJB container 308 of aWebApp container 310 .
- the containers communicate directlywiththe securityservice 314 (herein the same as security service 222 ), which in turn communicates with the Java security layer 302 and its security SPI's 304 . This allows the responsibility for secure authorization decisions to be moved from the application and placed in the security service layer.
- the invention is ideally suited to integrating the use of preexisting Java security SPI's 304 with custom SPI's 316 , 318 .
- Additional SPI's such as, for example, a connection filter, an access decision interface, an audit channel, and a certificate authenticator, may be included or integrated with the security server.
- the security service mediates access to the entire range of secured enterprise resources.
- FIG. 4 illustrates a process by which an application may use the invention to access a secure resource.
- a developer creates a customer application.
- the application may be one used by a physical user or customer, or may be an application interface program to allow another application to make use of the security server.
- the application is deployed within a container, the deployment process of which is disclosed in further detail below.
- the application then, in step 406 , accesses the security service using this container.
- the security service can interface directly with a set of J2EE compliant Java security features.
- the containers are used to allow access to a third-party or custom Security Provider Interface.
- the Security Provider Interface allows the application to access the secure resource, provided that the security service has indicated that the access requested should be allowed.
- FIG. 5 illustrates one embodiment of the deployment mechanism used to deploy an application within a container.
- data is registered in the security service 502 (herein the same as security service 314 ) for use by the application container 504 .
- the container reads the information from the deployment description 506 , and the actual container then does the enforcement. If there are different kinds of containers, one for WebApp, one for EJB, then there would need to be different implementation engines.
- the invention addresses this problem by first allowing the container reading the deployment descriptor to inform the security service of the security constraints and policies defined within, resulting in the population of security policies within the security service. Secondly, the container delegates all authorization decisions to the security service when the container later makes a request to access a protected resource, thus moving the point of enforcement from the container to the security service. The authorization decision is made by consulting the security constraints and policies provided through the deployment description, as well as any defined by the administrator through an administrative tool. A deployment tool can also be used to read the deployment descriptor and record the security information contained within into the security service, The deployment tool can then go directly to the security service, without reading the deployment descriptor.
- FIG. 6 illustrates a process by which data is entered into the security service during application deployment.
- the developer creates a deployment description.
- the description is passed to the container in step 604 , where the container analyzes the information to assess what information should be passed to the security service.
- the deployment description could be given to a deployment tool, in step 606 , that passes the information to the security service.
- FIG. 7 illustrates an example of a client using the security server in accordance with the invention to access a protected resource on the network or the server.
- the process starts with the client 702 making a request, which is one instance may be a simple case of the client authenticating itself.
- the client makes a connection to the container, indicated by the arrow 704 .
- a token 706 is passed along with the request.
- the system including the security server 710 ) makes a determination that the resource 708 is protected, so the client needs to authenticate.
- tokens represent the authenticated users of the client that are in turn being passed along in the invocation request to the container that the container will then use in the later step of calling the security service.
- the token represents the authenticated identity of the client itself.
- the client poses to the security service 712 (the same security service or security service 314 ) the question 714 , “Can the user identified by this token get access and perform the requested capabilities on the target resource?”
- the AC 716 does two things: it acts as a fanout spreading out through a series of Access Decision (AD) plug-ins 718 , 720 , 722 , and it also acts as an adjudicator.
- AD Access Decision
- the Access Decision passes the token along to each Access Decision in turn, beginning with the first one, Access Decision 718 , asking, “is this OK?”
- the Access Decision returns one of three responses: permit, deny, or abstain.
- the Access Controller then moves on to the next one if there is a next one, and so on until all Access Decisions have been polled. In effect the security mechanism acts like a series of panes of glass.
- An adjudication policy determines that if anyone says deny, then the process terminates, or simply returns an overall deny.
- the architecture allows for the adjudication policies which make this decision to be flexible enough that if X 718 is permit, and Y 720 is deny, and C 722 is abstain, then that can be considered a permit.
- Other implementations can take a more hard line: if there's any denying, it's an overall denial.
- An abstain is returned whenever the AC asks the access decision a question that the access decision doesn't exclusively understand, and hence cannot make an explicit decision.
- the access request may reach a point that nobody denies, some permit and some abstain, for example, where Y 720 abstains and X 718 and C 722 both permit.
- the adjudication policy can be then used to control how to determine the outcome. In one embodiment there are only two outcomes to the container: a permit or a deny. So the access controller looks at the adjudication policy to determine how that decision is made. For example in some, out of the box implementations, the system may use an adjudication policy which says, “do I require unanimous permission?” In which case, X, Y and C all have to permit. If any one of them does not permit, then the outcome is a deny. The other approach is to not require unanimous consent, in which case as long as no one denies then the access is allowed to occur. This decision is made based on the adjudication policy.
- the security service itself passes requests to the auditing subsystem 724 requesting that it audit what has just occurred and the outcome. Only at that point will the security service then tell the container that the final result is a permit or a deny. If it is permit, the container then allows the requested operation to be dispatched on to the protected resource. If it says deny, the request does not get to that point, and is immediately rejected.
- the invention also provides a method to call the Access Decision process on the way out i.e., following a successful receipt of an access request at the protected resource.
- the system went through the first checks on the request and everything was permitted, so the method was dispatched to the resource.
- the resource returns data that is intended to go out back to the client. Rather thanjust blindly returning this data back, the authorization check is rerun, this time allowing the security service, particularly the Access Decisions to look at the data to be returned to determine if its okay to return to the client.
- An example here is that of a business operation where a user is trying to request documents. When the user first enters they have a security clearance assigned to them, which means that they can look at documents that aren't classified above their security clearance.
- FIG. 8 illustrates a flowchart showing the process used by an embodiment of the invention in providing access to a secured or protected resource.
- the client develops and deploys the application within a container.
- a call is made and forwarded to the appropriate container shown by step 804 .
- the container is used to invoke the security service in step 806 .
- a fanout access controller determines which access decisions are to take place in verifying or acknowledging this particular access request.
- each Access Decision is selected, and processed or polled to determine its contribution to the access request, the output of each access decision being a deny, permit, or abstain.
- An audit mechanism tracks the outcome of each Access Decision in step 812 .
- step 814 Based on the outcome of the access decision and the cumulative response—be it permit, deny, or abstain—in step 814 the container is given (or denied) access to the protected resource.
- step 816 data can then be passed from the client application to the protected resource and vice versa. If the client later requests either to the same resource or a different resource (as determined in step 818 ), then the request is forwarded to the appropriate container and another authorization decision is required (step 820 ), otherwise the session terminates (step 822 ).
- FIG. 9 illustrates the security and personalization layers in accordance with one embodiment of the invention, including the entitlements layer 904 , and its positioning in relation to the business application layer 908 , business policies layer 906 and security authorization layer 902 .
- FIG. 9 shows how entitlements 904 can be used to transcend the boundary between the traditional security architecture (represented as 902 ), and the often-distinct business policy architecture (represented as 906 ).
- the information garnished through the use of such entitlements is used to direct the operation of a company's business applications represented as 908 , including personalizing them for individual entities based on that entity's entitlement.
- FIG. 10 shows how entitlements can be used to generate roles dynamically.
- An entitlement process 1002 allows a security question to be asked within a context.
- the invention includes an ability to dynamically assign roles to a particular subject 1000 , for example Principal 1 1004 , Principal 2 1006 , through Principal n 1008 , based on that entitlement, which further allows the system to provide an application context within the security layer, and allows authorization questions to be phrased in terms of the application.
- the system can only accurately answer those questions if they are presented in terms of the context, like the common example of a doctor and a patient. If the question is posed “Can Dr. Smith modify a patient's chart?”, then it is a context-less question. The traditional answer is “sometimes yes and sometimes no”.
- the only way to properly determine the answer is to know the context in which the question is asked, i.e., which patient are we talking about, and perhaps which chart.
- the system can then make role assignments like ownership or basically dynamic assignments that allows the system to make business decisions rather than security decisions.
- a developer can use the invention to personalize Web pages based on what a user is entitled to do.
- a self-registration or self-help feature can be made a part of a credit card website where, the user is the only one that can change their credit card numbers. Vendors can read them but they can't change them, and nobody else can see them. The system cannot figure out how to do this unless it knows the context. Can someone modify the credit card field? Of course someone can modify the credit card field. So, now, who can modify it? This is part of the context. Then the system must ask which particular one, because it can't just let any member modify any other member's credit card.
- a request may be a caller enrolled for the owner role.
- the system does not define the owner role, but it can have it dynamically associated to the user and then revoked from the user, as soon as they try to do something that they aren't the owner of anymore.
- Methodologies such as EJB can take advantage of this in that should the use be allowed to do something is based on whether or not you're in that role and you use the standard EJB to query that capability.
- a single sign-on mechanism which may combine elements of a traditional security implementation with elements of a business policy implementation.
- information received during an initial login process at a first security realm A 1102 for example a security realm which is provided by a third-party application and has no knowledge of a user's profile, or of a corporation's business policies, can be captured by a first login module 1108 , and passed (indicated by the arrow 1114 ) to a second login module 1110 in a second security realm 1104 .
- the second security realm B 1104 may have a knowledge ofthe business policies, and can determine or calculate entitlements or entitlement profiles 1102 for a user in addition to the original login information.
- the original login information, and the entitlement information (indicated by arrows 1118 and 1120 respectively) may be passed to a third login module 1112 in a third security realm C 1106 , and so on.
- SPI Security Provider Interfaces
- the JAAS Login Module used by the invention is based on the standard JAAS LoginModule, but additionally supports standard Login Module implementations.
- the authentication SPI is 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.
- the Authorization SPI provides for Access Decision, for which there is no Java equivalent sufficient.
- the Authorization SPI supports a variety of authorization models, both declarative and rules based.
- a callback handler can be used to obtain access to invocation context.
- the SPI also provides 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 includes making authorization decision of permit, deny, or abstain, or access requests for protected resources scoped by application.
- FIG. 11 illustrates an example of how the invention can be used to distribute profile information between security realms within a domain.
- the Auditing SPI includes an Audit Channel, for which no Java equivalent is defined.
- a callback handler is used to obtain access to invocation context including access to subject information, principal identities, group membership and role assignments, and user profile information (optional). Again, Multiple Audit Channel providers can be configured in stack.
- the responsibilities of the auditing SPI include determining if information should be audited, and performing the actual audit of the data based on QoS policies.
- the Principal->Role Mapping (JAAS LoginModule) SPI is based on the JAAS Login Module, and is 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.
- the Principal->Credential Mapping (JAAS LoginModule) SPI is based on the JAAS Login Module, and is 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
- the Java 2 KeyStore SPI is based on the Java 2 KeyStore interface, and provides consistent access to keys stored in a variety of medias, including File-based: (PKCS #5/#8, PKCS #12), HSM-based: (PKCS # 11 ), Smart Card/Java Card.
- the Key Storage SPI provides necessary support for code signing, and its responsibilities include retrieval of private key from protected storage, and retrieval of secrets from protected storage.
- the Certificate Retrieval SPI (CertPath) is based on JSR 55, and provides consistent mechanism to retrieve, verify, and revoke digital certificates, in addition to support for multiple certificate types.
- the responsibilities ofthe CertPath SPI include: CertStore: retrieval of certificates from store via query; CertPath: retrieval of chain of certificates utilizing CertStore; CertPathChecker: validates a certificate; and CertPathValidator: validate a chain of certificates.
- Certificate Mapping SPI (CertAuthenticator) for which no Java equivalent defined, provides an extensible means to allow mapping between digital certificates and principal identity within a security domain. It further provides verification and revocation checks performed prior to calling of CertAuthenticator The responsibilities of the certificate mapping SPI are based on a verified client's digital certificate, map to usemame and realm of principal.
- the Hardware Accelerator SPI uses Java Cryptographic Extensions, and is based on Java 2 security architecture. The responsibilities include providing cryptographic services under control of the security service.
- the Perimeter Protection SPI includes a Connection Filter to provide a built-in connection filter implementation. It is focused on ease of use, and is configurable from the console via Mbeans, allows continued support for user-written filters, and for cascading filters, each executed in turn. This minimizes conditions customers must handle.
- the Security Management SPI Integrate third-party vendors consoles into the server console and allows securityto redirect to servlets from these vendors.
- the security management SPI provides support for the full lifecycle of users, groups, roles, and authorization info.
- the Single Sign-on SPI uses LoginModule to map from the initiating principal's identity to resources identity, and to provide secure storage of resource credentials.
Abstract
A pluggable architecture allows security and business logic plugins to be inserted into a security service hosted by a server, and to control access to one or more secured resources on that server, on another server within the security domain, or between security domains. The security service may act as a focal point for security enforcement, and access rights determination, and information used or determined within one login process can flow transparently and automatically to other login processes. Entitlements denote what a particular user may or may not do with a particular resource, in a particular context. Entitlements reflect not only the technical aspects of the secure environment (the permit or deny concept), but can be used to represent the business logic or functionality required by the server provider. In this way entitlements bridge the gap between a simple security platform, and a complex business policy platform.
Description
- This application is a divisional of U.S. patent application Ser. No. 09/878,536, entitled “SYSTEM AND METHOD FOR SERVER SECURITY AND ENTITLEMENT PROCESSING,” by Paul B. Patrick, filed Jun. 11, 2001, 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 or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
- The invention is related generally to server security mechanisms, and specifically to an architecture for server security.
- Over the years the term “security” as applied to server technology, and particularly to e-commerce servers, has expanded to cover several aspects of a secure environment. The original definition of the term has always envisaged a mechanism for validating a particular user's (or client's) identity, and preventing that user from retrieving, viewing, or otherwise accessing, information on the server which they are not allowed to access.
-
FIG. 1 shows a typical example of a security mechanism commonly used today.Clients application server 106 via a number of protocols; including for example http (hypertext transfer protocol) 110 and IIOP (Internet Inter-ORB protocol) 112. The access requests are filtered through asecurity layer 108 which determines, typically based on a set of hardwired rules, whether to allow or disallow the requested access. The security layer may be a component of the protected resource (eg. the application server itself) or may operate as a separate entity (for example as part of a firewall system or device). - With current systems little or no attempt is made to analyze the nature of the access request, the type of client, or the type of protected resource. As such, security is often thought of as a simple “permit or deny” mechanism, designed in such a way as to understand the protected resources provided by the server, and to adhere to a predefined set of rules governing a user's or a client's access rights to those resources. There is little or no understanding of the manner in which the request is made, or the environmental setting in which a particular user may make a request to access a resource, and the security mechanism does not lend itself to easy modification of the rules to reflect new changes in business policy regarding security.
- Attempts have been made to develop the concept of security and particularly server security to include information that reflects a user's particular environment, and the manner in which a request to access a particular secure resource is phrased. Similarly, attempts have been made to provide security mechanisms that can be easily modified to reflect changes in business policy, security policy, and access rights. These methods still typically require an application programmer to be responsible for assembling a set of business policy queries together and asking the question, “is this OK ?—is this access acceptable according to the security rules?” What is needed is a mechanism to make this process all inclusive so that the programmer does not have to understand the business semantics and the business policy rules in order to be able to develop programs and applications that ask security related business policy questions.
- Recently, anew set of requirements concerning the securing of resources has emerged from discussions with application server customers and system integrators. These new requirements are expressed in terms of security from the point of view of an application instead of infrastructure. A key differentiation within these new requirements is the existence of business policy enforcement. The enforcement of business policy is typically described in terms of actions that a user is “entitled” to perform based on the role in which they are acting and the context of the business request. Customers and system integrators are frustrated with the fact that they are required to embed code that enforces business policy within applications. Embedding this type of logic creates deployment problems, in that the application must be modified, tested, and re-deployed each time the business policies are changed. Given the rate at which business policy changes, the current requirements for modification and re-deployment are unacceptable.
- Customers and system integrators would ideally like to have these new authorization capabilities universally applied across the different types of execution and resource containers, including for example those for Enterprise Java Bean (EJB), Web Applications (Servlet, JSP), as well as other types of business and resource containers. Role-based access control (RBAC) is becoming one of the primary form of authorization requested by customers and system integrators. The trend in use of roles allows organizational identity to be used as an abstract form of identity when making authorization decisions. The use of roles provides a mechanism to reduce both the cost and errors in the administration of application security since it simplifies the amount of administration.
- The Java 2 Enterprise Edition (J2EE) defines a declarative form of role-based access control. However, because it is based on a declarative scheme, the association of roles to principals is static. In addition, the current Java 2 Enterprise Edition specification provides no means by which the context of a business request, such as the parameters of the request or the identity of the target, can be taken into account when determining the roles to be associated with a given principal. Consequently, application developers are required to implement business policy rules within the application to compute dynamic roles associations in order to support concepts like “owner”.
- Customers and system integrators nowadays demand a richer set of authorization capabilities than those provided with the permission-based security defined by Java 2 security and the role-based access control defined in Java 2 Enterprise Edition. The foundation of the requirements for this richer level of authorization can be found in the intersection of classical authorization mechanisms, such as Access Control Lists, and business policy enforcement; and include the ability to take the context of the business request into consideration when making an authorization decision. The request context may include the identity of the target object, the value of the parameter of the request, and potentially environmental information such as the network or IP address of the initiating client.
- The lack of a single mechanism through which to integration these new authorization capabilities, regardless of execution or resource container type, is a point of frustration with customers and system integrators. The Service Provider Interface (SPI) is the mechanism used by several application servers, including the WebLogic Server product from BEA Systems, Inc., San Jose, Calif., to allow integration with external authorization providers. This SPI realm has a number of limitations that limit it's ability to be used as a successful means to integrate 3rd-party authorization mechanisms, or new authorization capabilities being required by customers and system integrators.
- One of the largest limitations with the current “realm” SPI is scope of enforcement. Currently, the enforcement scope of the realm mechanism does not cover resources such as Enterprise Java Bean and Web Applications. In particular, the realm is focused on RMI style resources such as JMS destinations, entries in JNDI, and servlets at a course-grained level. While the realm could conceivably be updated to hold the definition of the authorization policies required to support protection of such resources, it is the other limitations that ultimately make the realm an unrealistic mechanism to address all the authorization requirements.
- The second limitation of the current realm SPI is point of enforcement. The current realm mechanism does not allow the point at which the decision is made to allow access to a protected resource to exist within the realm itself. Instead, the point of enforcement is within the application server itself. Because of this approach, the current realm is defined to support only a permission-based authorization mechanism where the realm simply acts as a database of Access Control Lists. The complexities of providing a Java 2 Policy object that can also support the Java 2 sandbox rules is unacceptable to most vendors.
- Yet another limitation is the Enforcement Mechanism Support of the current realm SPI. As with the point of enforcement, the enforcement mechanisms allowed by the current realm SPI are limited to those based on permission-based authorization mechanisms. This is counter to the capabilities of the leading 3rd-party authorization providers, the integration of which is being requested by customers and systems integrators on a daily basis.
- JAVA, JAVA TWO ENTERPRISE EDITION (J2EE), and ENTERPRISE JAVABEANS (EJB) are trademarks of Sun Microsystems, Inc. WEBLOGIC is a trademark of BEA Systems, Inc.
- Together, these limitations constrain the types of authorization providers that can be integrated with an enterprise application server without minimizing the value proposition of the provider. There remains no current capability to obtain the context of the request in order to provide the rich authorization requested.
- The invention is related generally to server security mechanisms, and specifically to an architecture that provides for server security and entitlement processing. A pluggable architecture allows security and business logic plugins to be inserted into a security service hosted by a server, and to control access to one or more secured resources on that server, on another server within the security domain, or between security domains. The security service may act as a focal point for security enforcement, and access rights determination, and information used or determined within one login process can flow transparently and automatically to other login processes.
- The invention also introduces the concept of entitlements that are used within an access context. As used in the context of this application, a “user” or a “client” may refer to the same thing—either a physical person, a hardware device or software application under control of the physical person, or a hardware device or software application operating under autonomous control without user intervention. The user (or client) is the entity which is trying 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 etc.
- When the user attempts to access the resource, the security service may determine the type of access request, the destination (protected resource), and the setting in which the request is made—hereinafter referred to as the access context or simply the context. From this information the security service can determine an “entitlement”, or a set of entitlements, for the user. Entitlements clearly denote what a particular user may or may not do with a particular resource, in a particular context. Entitlements reflect not only the technical aspects of the secure environment (the permit or deny concept), but can be used to represent the business logic or functionality required by the server provider. In this way entitlements bridge the gap between a simple security platform, and a complex business policy platform.
- To illustrate the capability, consider the following business example: The answer to the question “Can Dr. Smith update a patient's medical chart” is dependent upon the context in which the question is asked. In a permission-based authorization system, this context is absent since the resource is some instance of a ‘medical chart’ object, the request is to ‘update’, and the Subject is ‘Dr. Smith’. Consequently, if the answer rendered is ‘Yes’, then Dr. Smith could update any patient's medical chart. In a capabilities-based authorization system, it is possible to add the necessary context of who's the patient in question. Thus, the question can now be rephrased as “Can Dr. Smith update Jon Joe's medical chart?” In determining the answer to this question, we now need to know if Dr. Smith is Jon Joe's personal physician, or perhaps an attending physician at a medical center. Using a simple rotation we can represent the concept as follows:
- In one embodiment, the invention comprises a security system for allowing a client to access a protected resource, comprising an application interface mechanism for receiving an access request from a client application to access a protected resource, and communicating said access request to a security service; a security service for making a decision to permit or deny said access request; and a resource interface for communicating permitted access requests to said protected resource.
- In another embodiment the invention comprises a method of allowing a client to access a protected resource, comprising receiving at an application interface mechanism an access request from a client application to access a protected resource and communicating said access request to a security service; making a decision at said security service to permit or deny said access request; and communicating via a resource interface a permitted access request to said protected resource.
-
FIG. 1 shows an illustration of a client/server architecture in accordance with the prior art. -
FIG. 2 shows an illustration of a client/server architecture in accordance with the invention. -
FIG. 3 shows an illustration of a security service in accordance with the invention. -
FIG. 4 shows a flowchart of a method used by the security service in accordance with the invention. -
FIG. 5 shows an illustration of a server security deployment tool and process in accordance with the invention. -
FIG. 6 shows a flowchart of a method used by the server security deployment tool in accordance with the invention. -
FIG. 7 shows an illustration of a security service and a protected resource in accordance with the invention. -
FIG. 8 shows a flowchart of a method used by the security service to allow access to a protected resource in accordance with the invention. -
FIG. 9 shows an illustration of a security layer in accordance with an embodiment of the invention. -
FIG. 10 shows an illustration of an entitlement mechanism in accordance with an embodiment of the invention. -
FIG. 11 shows an illustration of a login across several security domain models in accordance with the invention. - An embodiment of the invention includes a security architecture that provides for server security and entitlement processing, that allows security and business logic plugins to be inserted into a security service hosted by a server, and that can 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 acts 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.
- Except for the new terms that are defined below, the terms used in this document are consistent with terminology as defined in standard texts on Java, Enterprise Java Beans, WebLogic Server, and other generally accepted security concepts.
- access control—the restriction of access to resources to prevent its unauthorized use. access control information (ACI)—information about the initiator of a resource access request, used to make an access control enforcement decision.
- access control list (ACL)—the list of entities, together with their access rights, that are authorized to have access to a resource.
- authorization—the granting of authority, which includes the granting of access based on access rights.
- credentials—information describing the security attributes (identity and/or privileges) of a user or other principal. Credentials are claimed through authentication or delegation, and used by access control.
- delegation—the act whereby one user or principal authorizes another to use his (or hers or its) identity or privileges, perhaps with restrictions.
- entitlement—a right or permission granted to a principal.
- identity—a security attribute with the property of uniqueness; no two principals' identity may be identical. Principals may have several different kinds of identities, each unique.
- principal—a user or programmatic entity with the ability to use the resources of a system.
- role—an organizational identity that defines a set of allowable actions for an authorized user.
- Role Based Access Control (RBAC)—a class of security mechanisms that mediate access to resources though organizational identities called roles.
- security attributes—characteristics of a subject (user or principal) that form the basis of the system's policies governing that subject.
- security policy—the data that defines what protection a system's security services must provide. There are many kinds of security policy, including access control policy, audit policy, etc.
- Service Provider Interface (SPI)—a package or set of packages that support a concrete implementation of a subset of services.
- target—the final recipient in a delegation “call chain”. The only participant in a call-chain that is not an originator of a call.
- target object—the recipient of a business request message.
- trust model—a description of which components of the system and which entities outside the system must be trusted, and what they must be trusted for, if the system is to remain secure.
- Trusted Computing Base (TCB)—the portion of a system that must function correctly in order for the system to remain secure. A TCB should preferably be tamper-proof and its enforcement of policy should not be able to be circumvented.
- unauthenticated principal—a user or other principal who has not authenticated any identity or privilege.
- user—a human being using the system to issue requests to objects in order to get them to perform functions in the system on their behalf
- Embodiments of the invention described herein allow for the determination of entitlements as used within an access context. Typically, a user is trying 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 resource may be used while remaining within the spirit and scope of the invention. When the user attempts to access the resource, the security service determines 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 clearly denote what a particular user may do 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.
- Embodiments of the invention additionally 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))
- Resources (Remote Method Invocation (RMI), Java Messaging System (JMS))
- Embodiments of the invention also allow for the integration of external public key infrastructure to support such advanced features as:
- Certificate and key retrieval
- Certificate validation
- Revocation mechanisms (Certificate Revolution List (CRL), Online Certificate Status Protocol (OCSP))
- An important goal in developing the invention is 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. - Another important goal of the invention is 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.
- Security Domains
- As used in the context of the invention, a security realm or domain can span a single server, a plurality of servers, a cluster of servers, or a management domain. The invention allows for administrative control of identity propagation within, across, and between security domains. The identity of a client application or user can be propagated and scoped by the security domain. For example:
- Principal-Identity@security-domain-name
- When propagation is disabled, the initiating identity can be represented as being anonymous. For example:
- <anonymous>@initiating-security-domain-name
- Framework
- The security architecture or framework provided by the invention is intended to address the requirements put forth and many other things. Focusing exclusively on the authorization requirements, the security architecture attempts to provide the following capabilities in addition to a typical permission-based authorization:
- Dynamic Role Association
- Dynamic Role Association is a mechanism to allow a late binding of the association of roles to principals, that 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 occurs 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 is typically 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 ofmiles 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 is also 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 is in one embodiment, 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 are then 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
- Parametric Authorization is a mechanism that allows an authorization decision about a protected resource to be determined that is potentially based on the context of the request. Within the architecture provided by the invention, the scope of enforcement has been broadened to apply to all execution and resource containers. This is accomplished by having all execution and resource containers obtain authorization and role mapping services through an AccessController object provided by a Security Service. The AccessController utilizes the authorization services provided through the Service Provider Interfaces in order to provide the requested capabilities.
- The Service Provider Interfaces that actually define the mechanisms used to provide Dynamic Role Association and Parametric Authorization are 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.
- In addition, the methods defined on the Service Provider Interfaces that comprise the authorization framework 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 allows the delegated authorization approach to support both capabilities-based as well as permission-based implementations.
- Traditional security mechanisms tend to be context-less since they are based solely on permissions granted a principal for a given resource. Therefore, the only types of authorization decisions that can be made are whether the principal has the necessary permissions to access the resource. These types of authorization decisions are more complicated since they don't tend to represent business decisions. As a result, additional security checks are often required in application code to compensate for this limitation. For example, using traditional methods one could evaluate whether a principal is allowed to transfer money to a specific account. However, it is not possible to take into account the amount of the transfer, the currency of both the source and destination accounts, and the day of the week.
- In a parametric authorization based mechanism in accordance with the invention, the authorization decision is made using the context of the request, therefore the authorization decision more closely represent real business decisions. There is very little need for compensating security checks in the application itself. For example, using the invention 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
- While some other systems have tried to provide capabilities similar to the description of parametric authorization described above, these earlier systems and methods all require the caller to have previous knowledge of the parameters of the business policy being evaluated. The requirement for this knowledge presents virtually the same issue as that with making the authorization decision in application code-knowledge of some aspect of the business policies. Any time the business policy changes to require another piece of context information, the application must be modified and re-deployed.
- Addressing the issue of providing context information without prior knowledge of the business policy is accomplished by using callbacks to the containers from the authorization provider. While changing the type or number of parameters of a request fundamentally changes the application requires 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.
- The 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 is capable of requesting specific context information be returned. When the container's callback handler is called, the container responds 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 is aware of changes to business policy since they are queried for context information that is driven by the evaluation of specific business policy expressions.
- Functional Description
- Implementations of an entitlement processing engine (entitlement engine) that could be used to satisfy the requirements of parametric authorization must support the following requirements:
- An implementation should be able to specify 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 should be able to 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 should be in the form of a callback similar to that defined for JAAS. The implementation might callback for each piece of information individually, request multiple pieces of information in a single callback, or a combination of both.
- An implementation should be able to 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 should result in a boolean value that indicates whether the rule was successfully satisfied or not.
- The invention provides enterprise application developers with a framework architecture within which application implementations, particularly login, authorization, and auditing implementations, may 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.
- The framework architecture provided by the invention particularly allows Java developers to make use of existing Java security features, but to greatly expand the use of these security features in a manner that is transparent to the developer (or the user), and that can allow the security provided to be distributed throughout the enterprise without a need for additional layering or translation of security processes.
- Embodiments of the invention are particularly useful in the field of enterprise and server security and business workflow. Since the framework uses a pluggable architecture, it allows third-party vendors to provide security implementation plug-ins without a need for the core architecture to be modified. These plug-ins may include tools for digital certificate and key retrieval, certificate validation, and revocation mechanisms (e.g. CRL and OCSP). The pluggable framework architecture thus allows for the secure access control of enterprise resources, such as enterprise Java beans (EJB's), applications (including servlets and JSP's), and other networked resources (such as RMI, JNDI, and JMS destinations).
- Additionally, the framework architecture of the invention is especially suited to providing amethod of secure authorization and secure resource access throughout an enterprise-wide security domain. Each server with a domain may provide a different set of features, services and applications. The invention allows developers to deploy client applications which can make use of each server's particular services through a single sign-on mechanism that determines the client's access privileges throughout the domain or between cooperating domains.
-
FIG. 2 shows an example of a security architecture in accordance with an embodiment of the invention. As shown therein,clients 202, 204 (which may be either physical hardware clients or software applications) may attempt to access a secured service orresource 206, such as a persistent directory server, via a transaction orapplication server 208. An example of such a transaction server is the Weblogic Server product from BEA Systems Inc., San Jose, Calif., although the invention may be used with any other server product or equivalent system. Internet CORBA clients will typically attempt to make such an access through an Internet Inter-ORB Protocol (IIOP)request 212. Web clients will typically attempt to make an access through a series of hypertext transfer protocol (http) requests 210, either directly via aWeb server 214, or via a proxy plug-in 216 (in which case the proxy may also provide additional functionality, such as, for example, secure socket layer (SSL) encryption 218). In any case, the connection attempt is received by the transaction server, often via aninitial connection filter 220, and is passed to thesecurity service 222. In accordance with the invention, thesecurity service 222 is the focal point for security determination, including client and user level resource access, authorization, certification, privilege assessment and entitlement determination. Enterprise Java Beans (EJB's) 224, Web applications (WebApp's) 226, and other forms of applications may all use the security service through the use of containers. The security service handles calls from these containers to the protected resource, which in the case ofFIG. 2 . The calls may be handled by, for example, a plurality of managed beans (MBeans) 230, or the Java Named Directory Interface (JNDI) 232. -
FIG. 3 illustrates an embodiment of thesecurity service architecture 300 in greater detail. The security service augments the basic security services and features provided by the standard Java2 Enterprise Edition security set. As shown in this example, the basic Java security set 302 includes security provider interfaces 304 for key storage, authentication, certificate validation, and secure sockets, among others.Customer applications 306 may be written to directly take advantage of the Java security layer and these SPI's . The invention, as shown inFIG. 3 greatly enhances the developer's options in making use of these and other security features. In accordance with the invention, customer applications are deployed in containers, for example, anEJB container 308 of aWebApp container310. The containers communicate directlywiththe securityservice314 (herein the same as security service 222), which in turn communicates with theJava security layer 302 and its security SPI's 304. This allows the responsibility for secure authorization decisions to be moved from the application and placed in the security service layer. - In addition, the invention is ideally suited to integrating the use of preexisting Java security SPI's 304 with custom SPI's 316, 318. Additional SPI's such as, for example, a connection filter, an access decision interface, an audit channel, and a certificate authenticator, may be included or integrated with the security server. The security service mediates access to the entire range of secured enterprise resources.
-
FIG. 4 illustrates a process by which an application may use the invention to access a secure resource. Instep 402, a developer creates a customer application. The application may be one used by a physical user or customer, or may be an application interface program to allow another application to make use of the security server. Instep 404, the application is deployed within a container, the deployment process of which is disclosed in further detail below. The application then, instep 406, accesses the security service using this container. Optionally, instep 408, the security service can interface directly with a set of J2EE compliant Java security features. Alternatively, instep 410, the containers are used to allow access to a third-party or custom Security Provider Interface. Instep 412, the Security Provider Interface allows the application to access the secure resource, provided that the security service has indicated that the access requested should be allowed. -
FIG. 5 illustrates one embodiment of the deployment mechanism used to deploy an application within a container. As shown inFIG. 5 , data is registered in the security service 502 (herein the same as security service 314) for use by theapplication container 504. Traditionally, the container reads the information from thedeployment description 506, and the actual container then does the enforcement. If there are different kinds of containers, one for WebApp, one for EJB, then there would need to be different implementation engines. In addition there exists a series of resources inside of the J2EE environment that do not have a container, and that don't have deployment descriptors. The primary problem with this method is that various aspects of security are enforced in different ways within a single environment. The invention addresses this problem by first allowing the container reading the deployment descriptor to inform the security service of the security constraints and policies defined within, resulting in the population of security policies within the security service. Secondly, the container delegates all authorization decisions to the security service when the container later makes a request to access a protected resource, thus moving the point of enforcement from the container to the security service. The authorization decision is made by consulting the security constraints and policies provided through the deployment description, as well as any defined by the administrator through an administrative tool. A deployment tool can also be used to read the deployment descriptor and record the security information contained within into the security service, The deployment tool can then go directly to the security service, without reading the deployment descriptor. -
FIG. 6 illustrates a process by which data is entered into the security service during application deployment. Instep 602, the developer creates a deployment description. The description is passed to the container instep 604, where the container analyzes the information to assess what information should be passed to the security service. Optionally, the deployment description could be given to a deployment tool, instep 606, that passes the information to the security service. -
FIG. 7 illustrates an example of a client using the security server in accordance with the invention to access a protected resource on the network or the server. The process starts with the client 702 making a request, which is one instance may be a simple case of the client authenticating itself. The client makes a connection to the container, indicated by thearrow 704. A token 706 is passed along with the request. As a part of making the connection, the system (including the security server 710) makes a determination that theresource 708 is protected, so the client needs to authenticate. In this example, tokens represent the authenticated users of the client that are in turn being passed along in the invocation request to the container that the container will then use in the later step of calling the security service. In some embodiments the token represents the authenticated identity of the client itself. The client poses to the security service 712 (the same security service or security service 314) thequestion 714, “Can the user identified by this token get access and perform the requested capabilities on the target resource?” - To answer this question the security service uses an Access Controller, indicated as
AC 716 inFIG. 7 . TheAC 716 does two things: it acts as a fanout spreading out through a series of Access Decision (AD) plug-ins Access Decision 718, asking, “is this OK?” The Access Decision returns one of three responses: permit, deny, or abstain. The Access Controller then moves on to the next one if there is a next one, and so on until all Access Decisions have been polled. In effect the security mechanism acts like a series of panes of glass. IfX 718 says “permit” the process continues on; ifX 718 says “deny” the process stops. The AC then moves toAccess Decision Y 720 and asks the exact same question presenting the exact same identity, andY 720 similarly responds with a permit, deny or abstain. - This process continues for however many of these plug-ins the service has. An adjudication policy determines that if anyone says deny, then the process terminates, or simply returns an overall deny. The architecture allows for the adjudication policies which make this decision to be flexible enough that if
X 718 is permit, andY 720 is deny, andC 722 is abstain, then that can be considered a permit. Other implementations can take a more hard line: if there's any denying, it's an overall denial. An abstain is returned whenever the AC asks the access decision a question that the access decision doesn't exclusively understand, and hence cannot make an explicit decision. This is most common whenever a legacy authorization system is included that is needed for some but not all operations, or whenX 718 is corporate policy, andY 720 is line of business. In this case there may be questions asked that are enforced by corporate policy but not line of business, so the line of business decision maker says, “I don't understand this, I abstain”. - When all of the access decision makers are polled and no one up to the point where the request finally gets through says deny, then the access request may reach a point that nobody denies, some permit and some abstain, for example, where
Y 720 abstains and X 718 andC 722 both permit. The adjudication policy can be then used to control how to determine the outcome. In one embodiment there are only two outcomes to the container: a permit or a deny. So the access controller looks at the adjudication policy to determine how that decision is made. For example in some, out of the box implementations, the system may use an adjudication policy which says, “do I require unanimous permission?” In which case, X, Y and C all have to permit. If any one of them does not permit, then the outcome is a deny. The other approach is to not require unanimous consent, in which case as long as no one denies then the access is allowed to occur. This decision is made based on the adjudication policy. - No matter what happens within the access decision process the security service itself passes requests to the
auditing subsystem 724 requesting that it audit what has just occurred and the outcome. Only at that point will the security service then tell the container that the final result is a permit or a deny. If it is permit, the container then allows the requested operation to be dispatched on to the protected resource. If it says deny, the request does not get to that point, and is immediately rejected. - The invention also provides a method to call the Access Decision process on the way out i.e., following a successful receipt of an access request at the protected resource. In this scenario it can be assumed the system went through the first checks on the request and everything was permitted, so the method was dispatched to the resource. The resource returns data that is intended to go out back to the client. Rather thanjust blindly returning this data back, the authorization check is rerun, this time allowing the security service, particularly the Access Decisions to look at the data to be returned to determine if its okay to return to the client. An example here is that of a business operation where a user is trying to request documents. When the user first enters they have a security clearance assigned to them, which means that they can look at documents that aren't classified above their security clearance. If they only have a secret security clearance and the documents that were to be returned have top secret, then even though they got the method to run, the system would not want to allow the outcome to go back to the user because they would then be allowed to see something that they are not permitted to see. The Access Decisions are re-run again, this time reviewing the output that's going to go back to the user and make that same kind of decision. In this example there may be a lot of abstains, for example the
Y Access Decision 720 says, “I don't care what the output is going back, I only care about the input coming in”. The developer can mix and match plug-ins to achieve different policies based on line of business, or based on corporate policy. -
FIG. 8 illustrates a flowchart showing the process used by an embodiment of the invention in providing access to a secured or protected resource. Instep 802, the client develops and deploys the application within a container. When the application requires access to the protected resource, a call is made and forwarded to the appropriate container shown bystep 804. The container is used to invoke the security service instep 806. Within the security service, instep 808, a fanout access controller determines which access decisions are to take place in verifying or acknowledging this particular access request. Instep 810 each Access Decision is selected, and processed or polled to determine its contribution to the access request, the output of each access decision being a deny, permit, or abstain. An audit mechanism tracks the outcome of each Access Decision instep 812. Based on the outcome of the access decision and the cumulative response—be it permit, deny, or abstain—in step 814 the container is given (or denied) access to the protected resource. Instep 816 data can then be passed from the client application to the protected resource and vice versa. If the client later requests either to the same resource or a different resource (as determined in step 818), then the request is forwarded to the appropriate container and another authorization decision is required (step 820), otherwise the session terminates (step 822). -
FIG. 9 illustrates the security and personalization layers in accordance with one embodiment of the invention, including theentitlements layer 904, and its positioning in relation to thebusiness application layer 908,business policies layer 906 andsecurity authorization layer 902. It will be evident to one skilled in the art that the illustration shown inFIG. 9 is an abstract representation of how an entitlements layer may be developed, but that many other variations on this architecture can be used, and that such discrete layers might not (and in fact most likely would not) be used in any particular design implementation.FIG. 9 shows howentitlements 904 can be used to transcend the boundary between the traditional security architecture (represented as 902), and the often-distinct business policy architecture (represented as 906). The information garnished through the use of such entitlements is used to direct the operation of a company's business applications represented as 908, including personalizing them for individual entities based on that entity's entitlement. -
FIG. 10 shows how entitlements can be used to generate roles dynamically. Anentitlement process 1002 allows a security question to be asked within a context. The invention includes an ability to dynamically assign roles to a particular subject 1000, forexample Principal 1 1004,Principal 2 1006, throughPrincipal n 1008, based on that entitlement, which further allows the system to provide an application context within the security layer, and allows authorization questions to be phrased in terms of the application. The system can only accurately answer those questions if they are presented in terms of the context, like the common example of a doctor and a patient. If the question is posed “Can Dr. Smith modify a patient's chart?”, then it is a context-less question. The traditional answer is “sometimes yes and sometimes no”. The only way to properly determine the answer is to know the context in which the question is asked, i.e., which patient are we talking about, and perhaps which chart. The system can then make role assignments like ownership or basically dynamic assignments that allows the system to make business decisions rather than security decisions. - Using a simple notation we can represent the concept as follows:
- For each subject, an active role AR is one that the subject is currently using:
AR(s: subject)={active role for subject s} - Each subject may be associated with one or more authorized roles RA:
RA(s: subject)={authorized roles for subject s} - Each role may be authorized to perform one or more tasks TA:
TA(r: role)={tasks authorized for role r} - Subjects may execute tasks if the predicate function exec(s,t) is true at the current point in time with the current values:
exec(s: subject,t: task)=true iff subject s can execute task t - In order for the above statements to evaluate correctly, a couple of rules are required:
- 1. Role assignment—a subject can execute a transaction only if the subject has been assigned a role. The identification and authentication process are not considered part of the task, whereas all other activities performed on the system are conducted through tasks:
∀s: subject,t: task(exec(s,t)AR(s)≠0) - 2. Role authorization—a subject's active role must be authorized for the subject. This rule ensures that users can only take on roles for which they are authorized:
∀s: subject(AR(s)⊂RA(s)) - 3. Task authorization—a subject can execute a task only if the task is authorized for the subject's active role:
∀s: subject,t: task(exec(s,t)tεTA(AR(s))) - As another example, a developer can use the invention to personalize Web pages based on what a user is entitled to do. For example, a self-registration or self-help feature can be made a part of a credit card website where, the user is the only one that can change their credit card numbers. Vendors can read them but they can't change them, and nobody else can see them. The system cannot figure out how to do this unless it knows the context. Can someone modify the credit card field? Of course someone can modify the credit card field. So, now, who can modify it? This is part of the context. Then the system must ask which particular one, because it can't just let any member modify any other member's credit card. So the system must know which object is under consideration, and which profile so it can then ask, “are you the owner of that profile?” In the past the only thing defined were static roles. What the invention does through the use of entitlement is allow, business analysts and business policy makers to define dynamic roles which are computed at run time in order to define to the object or the principal identity. These roles do not violate the security specification of the underlying server architecture. For example, a request may be a caller enrolled for the owner role. The system does not define the owner role, but it can have it dynamically associated to the user and then revoked from the user, as soon as they try to do something that they aren't the owner of anymore. Methodologies such as EJB can take advantage of this in that should the use be allowed to do something is based on whether or not you're in that role and you use the standard EJB to query that capability.
- Another example of how the invention may be used is through the provision of a single sign-on mechanism, which may combine elements of a traditional security implementation with elements of a business policy implementation. As shown in
FIG. 11 , information received during an initial login process at a firstsecurity realm A 1102, for example a security realm which is provided by a third-party application and has no knowledge of a user's profile, or of a corporation's business policies, can be captured by afirst login module 1108, and passed (indicated by the arrow 1114) to asecond login module 1110 in asecond security realm 1104. The secondsecurity realm B 1104 may have a knowledge ofthe business policies, and can determine or calculate entitlements orentitlement profiles 1102 for a user in addition to the original login information. The original login information, and the entitlement information (indicated byarrows third login module 1112 in a thirdsecurity realm C 1106, and so on. - Security Provider Interfaces
- Security Provider Interfaces (SPI) that can be used with the invention include interfaces for:
- Authentication—Java Authentication and Authorization Service (JAAS) LoginModule
- Authorization—AccessDecision
- Auditing—AuditChannel
- Principal Mapping->Role Mapping—JAAS LoginModule
- Principal->Credentials Mapping—JAAS LoginModule
- Key Storage—
Java 2 KeyStoreSpi - Certificate Retrieval and Revocation—CertPath
- Certificate Mapping—CertAuthenticator
- Hardware Accelerators—Java Cryptographic Extensions
- Perimeter Protection—ConnectionFilter
- It will 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.
- Authentication SPI
- The JAAS Login Module used by the invention is based on the standard JAAS LoginModule, but additionally supports standard Login Module implementations. The authentication SPI is 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.
- Authorization SPI
- The Authorization SPI provides for Access Decision, for which there is no Java equivalent sufficient. The Authorization SPI supports a variety of authorization models, both declarative and rules based. A callback handler can be used to obtain access to invocation context. The SPI also provides 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 includes making authorization decision of permit, deny, or abstain, or access requests for protected resources scoped by application.
FIG. 11 illustrates an example of how the invention can be used to distribute profile information between security realms within a domain. - Auditing SPI
- The Auditing SPI includes an Audit Channel, for which no Java equivalent is defined. A callback handler is used to obtain access to invocation context including access to subject information, principal identities, group membership and role assignments, and user profile information (optional). Again, Multiple Audit Channel providers can be configured in stack. The responsibilities of the auditing SPI include determining if information should be audited, and performing the actual audit of the data based on QoS policies.
- Principal->Role Mapping SPI
- The Principal->Role Mapping (JAAS LoginModule) SPI is based on the JAAS Login Module, and is 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
- The Principal->Credential Mapping (JAAS LoginModule) SPI is based on the JAAS Login Module, and is 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
- Key Storage SPI
- The
Java 2 KeyStore SPI is based on theJava 2 KeyStore interface, and provides consistent access to keys stored in a variety of medias, including File-based: (PKCS #5/#8, PKCS #12), HSM-based: (PKCS #11), Smart Card/Java Card. The Key Storage SPI provides necessary support for code signing, and its responsibilities include retrieval of private key from protected storage, and retrieval of secrets from protected storage. - Certificate Retrieval SPI
- The Certificate Retrieval SPI (CertPath) is based on JSR 55, and provides consistent mechanism to retrieve, verify, and revoke digital certificates, in addition to support for multiple certificate types. The responsibilities ofthe CertPath SPI include: CertStore: retrieval of certificates from store via query; CertPath: retrieval of chain of certificates utilizing CertStore; CertPathChecker: validates a certificate; and CertPathValidator: validate a chain of certificates.
- Certificate Mapping SPI
- The Certificate Mapping SPI (CertAuthenticator) for which no Java equivalent defined, provides an extensible means to allow mapping between digital certificates and principal identity within a security domain. It further provides verification and revocation checks performed prior to calling of CertAuthenticator The responsibilities of the certificate mapping SPI are based on a verified client's digital certificate, map to usemame and realm of principal.
- Hardware Accelerator SPI
- The Hardware Accelerator SPI uses Java Cryptographic Extensions, and is based on
Java 2 security architecture. The responsibilities include providing cryptographic services under control of the security service. - Perimeter Protection SPI
- The Perimeter Protection SPI includes a Connection Filter to provide a built-in connection filter implementation. It is focused on ease of use, and is configurable from the console via Mbeans, allows continued support for user-written filters, and for cascading filters, each executed in turn. This minimizes conditions customers must handle.
- Security Management SPI
- The Security Management SPI Integrate third-party vendors consoles into the server console and allows securityto redirect to servlets from these vendors. The security management SPI provides support for the full lifecycle of users, groups, roles, and authorization info.
- Single Sign-on (SSO) SPI
- The Single Sign-on SPI uses LoginModule to map from the initiating principal's identity to resources identity, and to provide secure storage of resource credentials.
- The foregoing description ofpreferred embodiments ofthe 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. Obviously, many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles ofthe 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 equivalents.
Claims (5)
1. A method for determining user entitlements to access protected resources in a secure environment, comprising:
receiving an access request from a user application to access a protected resource, by invoking a security service with the access request and a callback;
determining user entitlements to access the protected resource, wherein the determining includes polling a plurality of security providers that may be plugged into the security service, and wherein the plurality of security providers use a callback handler to request context information from an application container for the access request;
making a decision at the security service based on the user entitlements to permit or deny the access request; and
the steps of either
(a) communicating a permitted access request to the protected resource, or
(b) denying a denied access request to the protected resource.
2. The method of claim 1 wherein if the access request is permitted, user entitlements also determine a type of access available to a user of the protected resource.
3. The method of claim 2 wherein the type of access includes any of view, modify, delete, or copy, any part or all of the protected resource.
4. The method of claim 1 wherein information about user entitlements can be communicated from a first security realm to a second security realm.
5. The method of claim 4 wherein additional information from a first security realm can be used to modify the user entitlements, prior to communicating the information about user entitlements from the first security realm to the second security realm.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/686,218 US20070157297A1 (en) | 2001-06-11 | 2007-03-14 | System and method for server security and entitlement processing |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/878,536 US7392546B2 (en) | 2001-06-11 | 2001-06-11 | System and method for server security and entitlement processing |
US11/686,218 US20070157297A1 (en) | 2001-06-11 | 2007-03-14 | System and method for server security and entitlement processing |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/878,536 Division US7392546B2 (en) | 2001-06-11 | 2001-06-11 | System and method for server security and entitlement processing |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070157297A1 true US20070157297A1 (en) | 2007-07-05 |
Family
ID=25372222
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/878,536 Expired - Lifetime US7392546B2 (en) | 2001-06-11 | 2001-06-11 | System and method for server security and entitlement processing |
US11/686,218 Abandoned US20070157297A1 (en) | 2001-06-11 | 2007-03-14 | System and method for server security and entitlement processing |
US12/142,451 Expired - Fee Related US7823189B2 (en) | 2001-06-11 | 2008-06-19 | System and method for dynamic role association |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/878,536 Expired - Lifetime US7392546B2 (en) | 2001-06-11 | 2001-06-11 | System and method for server security and entitlement processing |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/142,451 Expired - Fee Related US7823189B2 (en) | 2001-06-11 | 2008-06-19 | System and method for dynamic role association |
Country Status (6)
Country | Link |
---|---|
US (3) | US7392546B2 (en) |
EP (1) | EP1405457B1 (en) |
JP (1) | JP2004533075A (en) |
CN (1) | CN100361435C (en) |
AU (1) | AU2002310144B2 (en) |
WO (1) | WO2002101973A1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040019804A1 (en) * | 2002-07-24 | 2004-01-29 | Sun Microsystems, Inc. | System and method for processing callback requests included in web-based procedure calls through a firewall |
US20050237996A1 (en) * | 2004-04-21 | 2005-10-27 | Yokogawa Electric Corporation | Electronic apparatus system and data control apparatus |
US20060236380A1 (en) * | 2005-03-22 | 2006-10-19 | Dell Products L.P. | System and method for grouping device or application objects in a directory service |
US20080244688A1 (en) * | 2007-03-29 | 2008-10-02 | Mcclain Carolyn B | Virtualized federated role provisioning |
US20080244687A1 (en) * | 2007-03-29 | 2008-10-02 | Mcclain Carolyn B | Federated role provisioning |
US20080256616A1 (en) * | 2007-04-13 | 2008-10-16 | Microsoft Corporation | Unified authentication for web method platforms |
US20080256643A1 (en) * | 2007-04-13 | 2008-10-16 | Microsoft Corporation | Multiple entity authorization model |
US20100218238A1 (en) * | 2009-02-26 | 2010-08-26 | Genpact Global Holdings (Bermuda) Limited | Method and system for access control by using an advanced command interface server |
CN102694787A (en) * | 2011-03-22 | 2012-09-26 | 中华电信股份有限公司 | Authorization information exchange method |
US8874909B2 (en) | 2012-02-03 | 2014-10-28 | Daniel Joseph Lutz | System and method of storing data |
US10068102B2 (en) | 2010-06-28 | 2018-09-04 | International Business Machines Corporation | Dynamic, temporary data access token |
US10205786B2 (en) | 2016-04-22 | 2019-02-12 | Microsoft Technology Licensing, Llc | Multi-user application executing in user privilege mode |
US10886012B1 (en) | 2009-07-01 | 2021-01-05 | Vigilytics LLC | De-identifying medical history information for medical underwriting |
US10943028B1 (en) * | 2009-07-01 | 2021-03-09 | Vigilytics LLC | Using de-identified healthcare data to evaluate post-healthcare facility encounter treatment outcomes |
Families Citing this family (236)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7058817B1 (en) | 1999-07-02 | 2006-06-06 | The Chase Manhattan Bank | System and method for single sign on process for websites with multiple applications and services |
AU3438401A (en) | 1999-11-04 | 2001-05-14 | Jp Morgan Chase Bank | System and method for automated financial project management |
US10275780B1 (en) | 1999-11-24 | 2019-04-30 | Jpmorgan Chase Bank, N.A. | Method and apparatus for sending a rebate via electronic mail over the internet |
US8571975B1 (en) | 1999-11-24 | 2013-10-29 | Jpmorgan Chase Bank, N.A. | System and method for sending money via E-mail over the internet |
US7426530B1 (en) | 2000-06-12 | 2008-09-16 | Jpmorgan Chase Bank, N.A. | System and method for providing customers with seamless entry to a remote server |
US10185936B2 (en) | 2000-06-22 | 2019-01-22 | Jpmorgan Chase Bank, N.A. | Method and system for processing internet payments |
US8335855B2 (en) | 2001-09-19 | 2012-12-18 | Jpmorgan Chase Bank, N.A. | System and method for portal infrastructure tracking |
US8849716B1 (en) | 2001-04-20 | 2014-09-30 | Jpmorgan Chase Bank, N.A. | System and method for preventing identity theft or misuse by restricting access |
AU2002312381A1 (en) | 2001-06-07 | 2002-12-16 | First Usa Bank, N.A. | System and method for rapid updating of credit information |
US7392546B2 (en) * | 2001-06-11 | 2008-06-24 | Bea Systems, Inc. | System and method for server security and entitlement processing |
US7925616B2 (en) * | 2001-06-19 | 2011-04-12 | Microstrategy, Incorporated | Report system and method using context-sensitive prompt objects |
US7266839B2 (en) | 2001-07-12 | 2007-09-04 | J P Morgan Chase Bank | System and method for providing discriminated content to network users |
US8713623B2 (en) | 2001-09-20 | 2014-04-29 | Time Warner Cable Enterprises, LLC | Technique for effectively providing program material in a cable television system |
US7103576B2 (en) | 2001-09-21 | 2006-09-05 | First Usa Bank, Na | System for providing cardless payment |
WO2003036500A1 (en) * | 2001-10-24 | 2003-05-01 | Bea Systems, Inc. | System and method for application flow integration in a portal framework |
WO2003038561A2 (en) | 2001-11-01 | 2003-05-08 | First Usa Bank, N.A. | System and method for establishing or modifying an account with user selectable terms |
US7987501B2 (en) | 2001-12-04 | 2011-07-26 | Jpmorgan Chase Bank, N.A. | System and method for single session sign-on |
US20030126433A1 (en) * | 2001-12-27 | 2003-07-03 | Waikwan Hui | Method and system for performing on-line status checking of digital certificates |
US8256002B2 (en) * | 2002-01-18 | 2012-08-28 | Alcatel Lucent | Tool, method and apparatus for assessing network security |
JP2003233590A (en) * | 2002-02-08 | 2003-08-22 | Hitachi Ltd | Mobile follow-up service providing method, system and program |
US7941533B2 (en) | 2002-02-19 | 2011-05-10 | Jpmorgan Chase Bank, N.A. | System and method for single sign-on session management without central server |
US7552481B2 (en) * | 2002-03-18 | 2009-06-23 | Sun Microsystems, Inc. | Method of assessing an organization's network identity capability |
WO2003093964A1 (en) * | 2002-05-01 | 2003-11-13 | Bea Systems, Inc. | Enterprise application platform |
US7725560B2 (en) | 2002-05-01 | 2010-05-25 | Bea Systems Inc. | Web service-enabled portlet wizard |
US7058660B2 (en) | 2002-10-02 | 2006-06-06 | Bank One Corporation | System and method for network-based project management |
US7793342B1 (en) * | 2002-10-15 | 2010-09-07 | Novell, Inc. | Single sign-on with basic authentication for a transparent proxy |
US8301493B2 (en) | 2002-11-05 | 2012-10-30 | Jpmorgan Chase Bank, N.A. | System and method for providing incentives to consumers to share information |
US7779247B2 (en) | 2003-01-09 | 2010-08-17 | Jericho Systems Corporation | Method and system for dynamically implementing an enterprise resource policy |
US20060225138A1 (en) * | 2005-04-02 | 2006-10-05 | Takeshi Toyohara | End-to-end digital media entitlement system |
US8831966B2 (en) * | 2003-02-14 | 2014-09-09 | Oracle International Corporation | Method for delegated administration |
US7591000B2 (en) | 2003-02-14 | 2009-09-15 | Oracle International Corporation | System and method for hierarchical role-based entitlements |
US7653930B2 (en) | 2003-02-14 | 2010-01-26 | Bea Systems, Inc. | Method for role and resource policy management optimization |
US7840614B2 (en) | 2003-02-20 | 2010-11-23 | Bea Systems, Inc. | Virtual content repository application program interface |
US7293286B2 (en) | 2003-02-20 | 2007-11-06 | Bea Systems, Inc. | Federated management of content repositories |
US7610618B2 (en) * | 2003-02-24 | 2009-10-27 | Bea Systems, Inc. | System and method for authenticating a subject |
US7017051B2 (en) * | 2003-02-24 | 2006-03-21 | Bea Systems, Inc. | System and method for enterprise authentication |
US7810036B2 (en) | 2003-02-28 | 2010-10-05 | Bea Systems, Inc. | Systems and methods for personalizing a portal |
US7403925B2 (en) * | 2003-03-17 | 2008-07-22 | Intel Corporation | Entitlement security and control |
US7467414B2 (en) | 2003-03-17 | 2008-12-16 | Intel Corporation | Entitlement security and control for information system entitlement |
US7461395B2 (en) * | 2003-05-06 | 2008-12-02 | Oracle International Corporation | Distributed capability-based authorization architecture using roles |
US7404203B2 (en) * | 2003-05-06 | 2008-07-22 | Oracle International Corporation | Distributed capability-based authorization architecture |
EP1629382A4 (en) | 2003-06-02 | 2011-12-21 | Liquid Machines Inc | Managing data objects in dynamic, distributed and collaborative contexts |
US7469417B2 (en) * | 2003-06-17 | 2008-12-23 | Electronic Data Systems Corporation | Infrastructure method and system for authenticated dynamic security domain boundary extension |
US7363487B2 (en) * | 2003-07-01 | 2008-04-22 | International Business Machines Corporation | Method and system for dynamic client authentication in support of JAAS programming model |
JP2005085266A (en) * | 2003-09-04 | 2005-03-31 | Stmicroelectronics Sa | Access control of microprocessor peripheral device |
US20050081055A1 (en) * | 2003-10-10 | 2005-04-14 | Bea Systems, Inc. | Dynamically configurable distributed security system |
US20050251851A1 (en) * | 2003-10-10 | 2005-11-10 | Bea Systems, Inc. | Configuration of a distributed security system |
US8190893B2 (en) | 2003-10-27 | 2012-05-29 | Jp Morgan Chase Bank | Portable security transaction protocol |
US7284000B2 (en) * | 2003-12-19 | 2007-10-16 | International Business Machines Corporation | Automatic policy generation based on role entitlements and identity attributes |
US7543331B2 (en) * | 2003-12-22 | 2009-06-02 | Sun Microsystems, Inc. | Framework for providing a configurable firewall for computing systems |
US7313820B2 (en) * | 2003-12-29 | 2007-12-25 | International Business Machines Corporation | Method and system for providing an authorization framework for applications |
US20090119755A1 (en) * | 2004-02-04 | 2009-05-07 | Kodimer Marianne L | System and method for role based access control of a document processing device |
US7478421B2 (en) * | 2004-02-04 | 2009-01-13 | Toshiba Corporation | System and method for role based access control of a document processing device |
US7523486B1 (en) * | 2004-03-05 | 2009-04-21 | Sprint Communications Company Lp | User administration tool |
US7505972B1 (en) * | 2004-03-08 | 2009-03-17 | Novell, Inc. | Method and system for dynamic assignment of entitlements |
US7437736B2 (en) * | 2004-03-10 | 2008-10-14 | Citibank, N.A. | Method and apparatus for managing workflow in a single sign-on framework |
US7774601B2 (en) | 2004-04-06 | 2010-08-10 | Bea Systems, Inc. | Method for delegated administration |
US20050256906A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | Interface for portal and webserver administration-efficient updates |
US20050256899A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | System and method for representing hierarchical data structures |
US20050257154A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | Graphical association of elements for portal and webserver administration |
US20050257172A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | Interface for filtering for portal and webserver administration |
US20050262075A1 (en) * | 2004-05-21 | 2005-11-24 | Bea Systems, Inc. | Systems and methods for collaboration shared state management |
US8762981B2 (en) * | 2004-05-24 | 2014-06-24 | Sap Ag | Application loading and visualization |
US7721283B2 (en) | 2004-05-24 | 2010-05-18 | Sap Ag | Deploying a variety of containers in a Java 2 enterprise edition-based architecture |
US7735097B2 (en) * | 2004-05-24 | 2010-06-08 | Sap Ag | Method and system to implement a deploy service to perform deployment services to extend and enhance functionalities of deployed applications |
US7882502B2 (en) * | 2004-05-25 | 2011-02-01 | Sap Ag | Single file update |
US7747698B2 (en) * | 2004-05-25 | 2010-06-29 | Sap Ag | Transaction model for deployment operations |
US7877735B2 (en) * | 2004-05-25 | 2011-01-25 | Sap Ag | Application cloning |
US7650627B1 (en) * | 2004-05-28 | 2010-01-19 | Sap Ag | Abstract configuration files for efficient implementation of security services |
JP4527605B2 (en) * | 2004-06-21 | 2010-08-18 | 三星エスディアイ株式会社 | Electrolytic solution for lithium ion secondary battery and lithium ion secondary battery including the same |
US8312267B2 (en) | 2004-07-20 | 2012-11-13 | Time Warner Cable Inc. | Technique for securely communicating programming content |
US8266429B2 (en) | 2004-07-20 | 2012-09-11 | Time Warner Cable, Inc. | Technique for securely communicating and storing programming material in a trusted domain |
US7669226B2 (en) * | 2004-07-30 | 2010-02-23 | International Business Machines Corporation | Generic declarative authorization scheme for Java |
US8661420B2 (en) * | 2004-08-03 | 2014-02-25 | Oracle International Corporation | System and method for runtime interface versioning |
US7549054B2 (en) * | 2004-08-17 | 2009-06-16 | International Business Machines Corporation | System, method, service method, and program product for managing entitlement with identity and privacy applications for electronic commerce |
US8271527B2 (en) | 2004-08-26 | 2012-09-18 | Illinois Institute Of Technology | Refined permission constraints using internal and external data extraction in a role-based access control system |
US9032076B2 (en) * | 2004-10-22 | 2015-05-12 | International Business Machines Corporation | Role-based access control system, method and computer program product |
US7783670B2 (en) * | 2004-11-18 | 2010-08-24 | Bea Systems, Inc. | Client server conversion for representing hierarchical data structures |
US9723267B2 (en) | 2004-12-15 | 2017-08-01 | Time Warner Cable Enterprises Llc | Method and apparatus for wideband distribution of content |
US7562382B2 (en) * | 2004-12-16 | 2009-07-14 | International Business Machines Corporation | Specializing support for a federation relationship |
US7810105B2 (en) * | 2004-12-29 | 2010-10-05 | Motorola, Inc. | Method and apparatus for running different types of applications on a wireless mobile device |
US20060156418A1 (en) * | 2005-01-10 | 2006-07-13 | Ibm Corporation | Method and apparatus for preventing unauthorized access to data |
FR2881854B1 (en) * | 2005-02-04 | 2008-01-11 | Radiotelephone Sfr | METHOD FOR SECURELY MANAGING THE EXECUTION OF AN APPLICATION |
JP2006268125A (en) * | 2005-03-22 | 2006-10-05 | Fuji Electric Systems Co Ltd | Application server and its program |
US7748026B1 (en) * | 2005-03-30 | 2010-06-29 | Sprint Communications Company L.P. | Transparent interceptors for privacy policy implementation |
US8078740B2 (en) | 2005-06-03 | 2011-12-13 | Microsoft Corporation | Running internet applications with low rights |
US7571473B1 (en) | 2005-06-10 | 2009-08-04 | Sprint Communications Company L.P. | Identity management system and method |
US20060287593A1 (en) * | 2005-06-20 | 2006-12-21 | General Electric Company | System and method providing communication in a medical imaging system |
US8185877B1 (en) | 2005-06-22 | 2012-05-22 | Jpmorgan Chase Bank, N.A. | System and method for testing applications |
US20070022459A1 (en) | 2005-07-20 | 2007-01-25 | Gaebel Thomas M Jr | Method and apparatus for boundary-based network operation |
US20070033196A1 (en) * | 2005-08-02 | 2007-02-08 | Sap Ag | Service directory |
US20070033571A1 (en) * | 2005-08-02 | 2007-02-08 | Sap Ag | Dynamic work center |
US7752450B1 (en) | 2005-09-14 | 2010-07-06 | Juniper Networks, Inc. | Local caching of one-time user passwords |
US8583926B1 (en) | 2005-09-19 | 2013-11-12 | Jpmorgan Chase Bank, N.A. | System and method for anti-phishing authentication |
US7917537B2 (en) | 2005-09-26 | 2011-03-29 | Oracle International Corporation | System and method for providing link property types for content management |
US7953734B2 (en) | 2005-09-26 | 2011-05-31 | Oracle International Corporation | System and method for providing SPI extensions for content management system |
US7752205B2 (en) | 2005-09-26 | 2010-07-06 | Bea Systems, Inc. | Method and system for interacting with a virtual content repository |
US7818344B2 (en) | 2005-09-26 | 2010-10-19 | Bea Systems, Inc. | System and method for providing nested types for content management |
US8001610B1 (en) * | 2005-09-28 | 2011-08-16 | Juniper Networks, Inc. | Network defense system utilizing endpoint health indicators and user identity |
US20070079373A1 (en) * | 2005-10-04 | 2007-04-05 | Computer Associates Think, Inc. | Preventing the installation of rootkits using a master computer |
US8635660B2 (en) * | 2005-12-06 | 2014-01-21 | Oracle International Corporation | Dynamic constraints for query operations |
US7945960B2 (en) * | 2005-12-06 | 2011-05-17 | Oracle International Corporation | Dynamic conditional security policy extensions |
US8042151B2 (en) * | 2005-12-20 | 2011-10-18 | Microsoft Corporation | Application context based access control |
US7882538B1 (en) | 2006-02-02 | 2011-02-01 | Juniper Networks, Inc. | Local caching of endpoint security information |
US7873967B2 (en) * | 2006-02-27 | 2011-01-18 | Microsoft Corporation | Pluggable business logic |
US8280982B2 (en) | 2006-05-24 | 2012-10-02 | Time Warner Cable Inc. | Personal content server apparatus and methods |
US9386327B2 (en) | 2006-05-24 | 2016-07-05 | Time Warner Cable Enterprises Llc | Secondary content insertion apparatus and methods |
US8024762B2 (en) | 2006-06-13 | 2011-09-20 | Time Warner Cable Inc. | Methods and apparatus for providing virtual content over a network |
US8185737B2 (en) | 2006-06-23 | 2012-05-22 | Microsoft Corporation | Communication across domains |
US8793490B1 (en) | 2006-07-14 | 2014-07-29 | Jpmorgan Chase Bank, N.A. | Systems and methods for multifactor authentication |
US7904953B2 (en) * | 2006-09-22 | 2011-03-08 | Bea Systems, Inc. | Pagelets |
US8463852B2 (en) | 2006-10-06 | 2013-06-11 | Oracle International Corporation | Groupware portlets for integrating a portal with groupware systems |
US8520850B2 (en) | 2006-10-20 | 2013-08-27 | Time Warner Cable Enterprises Llc | Downloadable security and protection methods and apparatus |
US8732854B2 (en) | 2006-11-01 | 2014-05-20 | Time Warner Cable Enterprises Llc | Methods and apparatus for premises content distribution |
US20080109292A1 (en) * | 2006-11-03 | 2008-05-08 | Sap Ag | Voice-enabled workflow item interface |
US8424077B2 (en) * | 2006-12-18 | 2013-04-16 | Irdeto Canada Corporation | Simplified management of authentication credentials for unattended applications |
US8621540B2 (en) | 2007-01-24 | 2013-12-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for provisioning in a download-enabled system |
US8181206B2 (en) | 2007-02-28 | 2012-05-15 | Time Warner Cable Inc. | Personal content server apparatus and methods |
DE102007012749A1 (en) * | 2007-03-16 | 2008-09-18 | Siemens Ag | Method and system for providing services to terminals |
US20100324953A1 (en) * | 2007-03-30 | 2010-12-23 | Real Enterprise Solutions Development B.V. | Method and system for determining entitlements to resources of an organization |
US8904391B2 (en) * | 2007-04-23 | 2014-12-02 | International Business Machines Corporation | Policy-based access control approach to staff activities of a business process |
US8473735B1 (en) | 2007-05-17 | 2013-06-25 | Jpmorgan Chase | Systems and methods for managing digital certificates |
US7979893B2 (en) * | 2007-05-31 | 2011-07-12 | Microsoft Corporation | Tailored system management interface |
US8806637B2 (en) * | 2007-06-11 | 2014-08-12 | Red Hat, Inc. | Authorization framework |
US10019570B2 (en) * | 2007-06-14 | 2018-07-10 | Microsoft Technology Licensing, Llc | Protection and communication abstractions for web browsers |
US7886335B1 (en) | 2007-07-12 | 2011-02-08 | Juniper Networks, Inc. | Reconciliation of multiple sets of network access control policies |
US20090019427A1 (en) * | 2007-07-13 | 2009-01-15 | International Business Machines Corporation | Method and Apparatus for Providing Requirement Driven Static Analysis of Test Coverage for Web-Based, Distributed Processes |
US9704162B2 (en) * | 2007-08-20 | 2017-07-11 | Oracle International Corporation | Enterprise structure configurator |
US9160752B2 (en) * | 2007-08-31 | 2015-10-13 | International Business Machines Corporation | Database authorization rules and component logic authorization rules aggregation |
US9171344B2 (en) | 2007-10-30 | 2015-10-27 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US8065166B2 (en) | 2007-10-30 | 2011-11-22 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US8635618B2 (en) * | 2007-11-20 | 2014-01-21 | International Business Machines Corporation | Method and system to identify conflicts in scheduling data center changes to assets utilizing task type plugin with conflict detection logic corresponding to the change request |
US8321682B1 (en) | 2008-01-24 | 2012-11-27 | Jpmorgan Chase Bank, N.A. | System and method for generating and managing administrator passwords |
US8510796B2 (en) * | 2008-01-25 | 2013-08-13 | Oracle International Corporation | Method for application-to-application authentication via delegation |
US9503691B2 (en) | 2008-02-19 | 2016-11-22 | Time Warner Cable Enterprises Llc | Methods and apparatus for enhanced advertising and promotional delivery in a network |
JP2009259198A (en) * | 2008-03-27 | 2009-11-05 | Hitachi Ltd | Information processing restriction system, device, and program |
US8056119B2 (en) * | 2008-04-25 | 2011-11-08 | Oracle America, Inc. | Method and system for controlling inter-zone communication |
US20090320125A1 (en) * | 2008-05-08 | 2009-12-24 | Eastman Chemical Company | Systems, methods, and computer readable media for computer security |
US9092243B2 (en) | 2008-05-28 | 2015-07-28 | Red Hat, Inc. | Managing a software appliance |
US10657466B2 (en) | 2008-05-29 | 2020-05-19 | Red Hat, Inc. | Building custom appliances in a cloud-based network |
US8868721B2 (en) | 2008-05-29 | 2014-10-21 | Red Hat, Inc. | Software appliance management using broadcast data |
US20100031227A1 (en) * | 2008-08-01 | 2010-02-04 | International Business Machines Corporation | Structured Representation of Integration Scenarios of Software Products |
US20100049573A1 (en) * | 2008-08-20 | 2010-02-25 | Oracle International Corporation | Automated security provisioning for outsourced operations |
US9357247B2 (en) | 2008-11-24 | 2016-05-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for content delivery and message exchange across multiple content delivery networks |
US9210173B2 (en) * | 2008-11-26 | 2015-12-08 | Red Hat, Inc. | Securing appliances for use in a cloud computing environment |
US8745361B2 (en) * | 2008-12-02 | 2014-06-03 | Microsoft Corporation | Sandboxed execution of plug-ins |
KR101224717B1 (en) * | 2008-12-26 | 2013-01-21 | 에스케이플래닛 주식회사 | Method for Protecting Software License, System, Server, Terminal And Computer-Readable Recording Medium with Program therefor |
US20100192193A1 (en) * | 2009-01-23 | 2010-07-29 | Microsoft Corporation | Security restriction techniques for browser-based applications |
US8272065B2 (en) * | 2009-03-11 | 2012-09-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Secure client-side aggregation of web applications |
US11076189B2 (en) | 2009-03-30 | 2021-07-27 | Time Warner Cable Enterprises Llc | Personal media channel apparatus and methods |
US9215423B2 (en) | 2009-03-30 | 2015-12-15 | Time Warner Cable Enterprises Llc | Recommendation engine apparatus and methods |
WO2010126797A1 (en) | 2009-04-29 | 2010-11-04 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
GB2505375B (en) * | 2009-05-05 | 2014-04-09 | Egress Software Technologies Ltd | Secure data exchange desktop |
US9866609B2 (en) | 2009-06-08 | 2018-01-09 | Time Warner Cable Enterprises Llc | Methods and apparatus for premises content distribution |
US9602864B2 (en) | 2009-06-08 | 2017-03-21 | Time Warner Cable Enterprises Llc | Media bridge apparatus and methods |
US20100325684A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Role-based security for messaging administration and management |
US9608826B2 (en) | 2009-06-29 | 2017-03-28 | Jpmorgan Chase Bank, N.A. | System and method for partner key management |
US20100332544A1 (en) * | 2009-06-29 | 2010-12-30 | Collins Mark A | Surrogate Management Capabilities For Heterogeneous Systems Management Support |
US8489685B2 (en) | 2009-07-17 | 2013-07-16 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US8977705B2 (en) * | 2009-07-27 | 2015-03-10 | Verisign, Inc. | Method and system for data logging and analysis |
US9237381B2 (en) | 2009-08-06 | 2016-01-12 | Time Warner Cable Enterprises Llc | Methods and apparatus for local channel insertion in an all-digital content distribution network |
US8250628B2 (en) * | 2009-08-28 | 2012-08-21 | International Business Machines Corporation | Dynamic augmentation, reduction, and/or replacement of security information by evaluating logical expressions |
WO2011030755A1 (en) * | 2009-09-10 | 2011-03-17 | 日本電気株式会社 | Role setting device, role setting method and role setting program |
US8396055B2 (en) | 2009-10-20 | 2013-03-12 | Time Warner Cable Inc. | Methods and apparatus for enabling media functionality in a content-based network |
US10264029B2 (en) | 2009-10-30 | 2019-04-16 | Time Warner Cable Enterprises Llc | Methods and apparatus for packetized content delivery over a content delivery network |
US9635421B2 (en) | 2009-11-11 | 2017-04-25 | Time Warner Cable Enterprises Llc | Methods and apparatus for audience data collection and analysis in a content delivery network |
US9519728B2 (en) | 2009-12-04 | 2016-12-13 | Time Warner Cable Enterprises Llc | Apparatus and methods for monitoring and optimizing delivery of content in a network |
EP2339513A1 (en) * | 2009-12-08 | 2011-06-29 | Postech Academy-Industry- Foundation | Apparatus and method for creating and managing personalized services in communication system |
US8332917B2 (en) * | 2009-12-29 | 2012-12-11 | International Business Machines Corporation | Providing secure dynamic role selection and managing privileged user access from a client device |
US9342661B2 (en) | 2010-03-02 | 2016-05-17 | Time Warner Cable Enterprises Llc | Apparatus and methods for rights-managed content and data delivery |
US20110296523A1 (en) * | 2010-05-26 | 2011-12-01 | Microsoft Corporation | Access control management mapping resource/action pairs to principals |
US9300445B2 (en) | 2010-05-27 | 2016-03-29 | Time Warner Cable Enterprise LLC | Digital domain content processing and distribution apparatus and methods |
US9906838B2 (en) | 2010-07-12 | 2018-02-27 | Time Warner Cable Enterprises Llc | Apparatus and methods for content delivery and message exchange across multiple content delivery networks |
US8997136B2 (en) | 2010-07-22 | 2015-03-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for packetized content delivery over a bandwidth-efficient network |
US9185341B2 (en) | 2010-09-03 | 2015-11-10 | Time Warner Cable Enterprises Llc | Digital domain content processing and distribution apparatus and methods |
US8930979B2 (en) | 2010-11-11 | 2015-01-06 | Time Warner Cable Enterprises Llc | Apparatus and methods for identifying and characterizing latency in a content delivery network |
US10148623B2 (en) | 2010-11-12 | 2018-12-04 | Time Warner Cable Enterprises Llc | Apparatus and methods ensuring data privacy in a content distribution network |
US8793706B2 (en) | 2010-12-16 | 2014-07-29 | Microsoft Corporation | Metadata-based eventing supporting operations on data |
CN102148819B (en) * | 2010-12-31 | 2013-12-11 | 无锡华御信息技术有限公司 | Information leakage-prevention collaborative office security system and method |
US9602414B2 (en) | 2011-02-09 | 2017-03-21 | Time Warner Cable Enterprises Llc | Apparatus and methods for controlled bandwidth reclamation |
US9064033B2 (en) * | 2011-07-05 | 2015-06-23 | International Business Machines Corporation | Intelligent decision support for consent management |
US9021017B2 (en) * | 2011-09-03 | 2015-04-28 | Barracuda Networks, Inc. | Configuring a plurality of diverse devices/services from an adaptive configuration control hyper-server apparatus |
US8914502B2 (en) * | 2011-09-27 | 2014-12-16 | Oracle International Corporation | System and method for dynamic discovery of origin servers in a traffic director environment |
US9069947B2 (en) | 2011-09-29 | 2015-06-30 | Oracle International Corporation | Privileged account manager, access management |
CN103095661A (en) * | 2011-11-01 | 2013-05-08 | 镇江华扬信息科技有限公司 | Single sign on (SSO) achievement method based on Javascript wormhole technology |
US8811177B1 (en) | 2011-11-03 | 2014-08-19 | Jpmorgan Chase Bank, N.A. | Method and system for implementing a network analysis tool for endpoints deployments |
WO2013095411A1 (en) * | 2011-12-21 | 2013-06-27 | Intel Corporation | INCORPORATING ACCESS CONTROL FUNCTIONALITY INTO A SYSTEM ON A CHIP (SoC) |
US20130218918A1 (en) * | 2012-02-16 | 2013-08-22 | Microsoft Corporation | Claim based execution control |
US9467723B2 (en) | 2012-04-04 | 2016-10-11 | Time Warner Cable Enterprises Llc | Apparatus and methods for automated highlight reel creation in a content delivery network |
US8745718B1 (en) | 2012-08-20 | 2014-06-03 | Jericho Systems Corporation | Delivery of authentication information to a RESTful service using token validation scheme |
US20140082645A1 (en) | 2012-09-14 | 2014-03-20 | Peter Stern | Apparatus and methods for providing enhanced or interactive features |
US9565472B2 (en) | 2012-12-10 | 2017-02-07 | Time Warner Cable Enterprises Llc | Apparatus and methods for content transfer protection |
JP5930203B2 (en) | 2012-12-11 | 2016-06-08 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | Method for controlling access to service, computer and computer program thereof |
US20140282786A1 (en) | 2013-03-12 | 2014-09-18 | Time Warner Cable Enterprises Llc | Methods and apparatus for providing and uploading content to personalized network storage |
US10368255B2 (en) | 2017-07-25 | 2019-07-30 | Time Warner Cable Enterprises Llc | Methods and apparatus for client-based dynamic control of connections to co-existing radio access networks |
US9066153B2 (en) | 2013-03-15 | 2015-06-23 | Time Warner Cable Enterprises Llc | Apparatus and methods for multicast delivery of content in a content delivery network |
US9419957B1 (en) | 2013-03-15 | 2016-08-16 | Jpmorgan Chase Bank, N.A. | Confidence-based authentication |
US9275221B2 (en) * | 2013-05-01 | 2016-03-01 | Globalfoundries Inc. | Context-aware permission control of hybrid mobile applications |
US9961052B2 (en) * | 2013-06-28 | 2018-05-01 | Extreme Networks, Inc. | Virtualized host ID key sharing |
US9430665B2 (en) | 2013-07-22 | 2016-08-30 | Siemens Aktiengesellschaft | Dynamic authorization to features and data in JAVA-based enterprise applications |
US9313568B2 (en) | 2013-07-23 | 2016-04-12 | Chicago Custom Acoustics, Inc. | Custom earphone with dome in the canal |
WO2015012867A1 (en) | 2013-07-26 | 2015-01-29 | Hewlett Packard Development Company, L.P. | Data view based on context |
US9667610B2 (en) | 2013-09-19 | 2017-05-30 | Oracle International Corporation | Privileged account plug-in framework—network—connected objects |
US9602545B2 (en) * | 2014-01-13 | 2017-03-21 | Oracle International Corporation | Access policy management using identified roles |
US9230134B1 (en) * | 2014-01-17 | 2016-01-05 | Google Inc. | Privacy setting metadata for application developers |
US10148726B1 (en) | 2014-01-24 | 2018-12-04 | Jpmorgan Chase Bank, N.A. | Initiating operating system commands based on browser cookies |
US9450820B2 (en) | 2014-02-26 | 2016-09-20 | International Business Machines Corporation | Dynamic extensible application server management |
US9300652B2 (en) * | 2014-04-14 | 2016-03-29 | Adobe Systems Incorporated | Scoped access to user content |
US9621940B2 (en) | 2014-05-29 | 2017-04-11 | Time Warner Cable Enterprises Llc | Apparatus and methods for recording, accessing, and delivering packetized content |
US11540148B2 (en) | 2014-06-11 | 2022-12-27 | Time Warner Cable Enterprises Llc | Methods and apparatus for access point location |
US9985992B1 (en) * | 2014-09-19 | 2018-05-29 | Jpmorgan Chase Bank, N.A. | Entitlement system and method |
US9935833B2 (en) | 2014-11-05 | 2018-04-03 | Time Warner Cable Enterprises Llc | Methods and apparatus for determining an optimized wireless interface installation configuration |
US10116676B2 (en) | 2015-02-13 | 2018-10-30 | Time Warner Cable Enterprises Llc | Apparatus and methods for data collection, analysis and service modification based on online activity |
CN106487743B (en) * | 2015-08-25 | 2020-02-21 | 阿里巴巴集团控股有限公司 | Method and apparatus for supporting multi-user cluster identity verification |
US9986578B2 (en) | 2015-12-04 | 2018-05-29 | Time Warner Cable Enterprises Llc | Apparatus and methods for selective data network access |
US9918345B2 (en) | 2016-01-20 | 2018-03-13 | Time Warner Cable Enterprises Llc | Apparatus and method for wireless network services in moving vehicles |
US10404758B2 (en) | 2016-02-26 | 2019-09-03 | Time Warner Cable Enterprises Llc | Apparatus and methods for centralized message exchange in a user premises device |
US10492034B2 (en) | 2016-03-07 | 2019-11-26 | Time Warner Cable Enterprises Llc | Apparatus and methods for dynamic open-access networks |
US20170329985A1 (en) | 2016-05-10 | 2017-11-16 | Cyber-Ark Software Ltd. | Application control |
US10909265B2 (en) * | 2016-06-10 | 2021-02-02 | OneTrust, LLC | Application privacy scanning systems and related methods |
US11392720B2 (en) | 2016-06-10 | 2022-07-19 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11188615B2 (en) | 2016-06-10 | 2021-11-30 | OneTrust, LLC | Data processing consent capture systems and related methods |
US10164858B2 (en) | 2016-06-15 | 2018-12-25 | Time Warner Cable Enterprises Llc | Apparatus and methods for monitoring and diagnosing a wireless network |
US10756909B2 (en) * | 2016-12-06 | 2020-08-25 | Veniam, Inc. | Systems and methods for self and automated management of certificates in a network of moving things, for example including a network of autonomous vehicles |
US10645547B2 (en) | 2017-06-02 | 2020-05-05 | Charter Communications Operating, Llc | Apparatus and methods for providing wireless service in a venue |
US10638361B2 (en) | 2017-06-06 | 2020-04-28 | Charter Communications Operating, Llc | Methods and apparatus for dynamic control of connections to co-existing radio access networks |
US11070559B2 (en) * | 2017-08-23 | 2021-07-20 | Oracle International Corporation | System and method for supporting object-based security |
US11501351B2 (en) * | 2018-03-21 | 2022-11-15 | Cdk Global, Llc | Servers, systems, and methods for single sign-on of an automotive commerce exchange |
US11190608B2 (en) | 2018-03-21 | 2021-11-30 | Cdk Global Llc | Systems and methods for an automotive commerce exchange |
CN109948360B (en) * | 2019-02-26 | 2023-04-07 | 维正知识产权科技有限公司 | Multi-control-domain security kernel construction method and system for complex scene |
US11397794B1 (en) * | 2019-03-25 | 2022-07-26 | Amazon Technologies, Inc. | Automated role management for resource accessing code |
US11184351B2 (en) * | 2019-09-04 | 2021-11-23 | Bank Of America Corporation | Security tool |
US11514021B2 (en) | 2021-01-22 | 2022-11-29 | Cdk Global, Llc | Systems, methods, and apparatuses for scanning a legacy database |
CN112579872B (en) * | 2021-03-01 | 2021-07-09 | 杭州筋斗腾云科技有限公司 | Network resource access intermediary system based on resource plug-in and processing method thereof |
US11803535B2 (en) | 2021-05-24 | 2023-10-31 | Cdk Global, Llc | Systems, methods, and apparatuses for simultaneously running parallel databases |
US20230095155A1 (en) * | 2021-09-28 | 2023-03-30 | Docusign, Inc. | Delegated signing using sensitivity classification |
Citations (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5369702A (en) * | 1993-10-18 | 1994-11-29 | Tecsec Incorporated | Distributed cryptographic object method |
US5551040A (en) * | 1993-06-02 | 1996-08-27 | Lucent Technologies Inc. | Methods and apparatus for specifying the contexts of names in callback-style programming |
US5764958A (en) * | 1995-11-30 | 1998-06-09 | International Business Machines Corporation | Method and apparatus for creating dynamic roles with a system object model |
US5848352A (en) * | 1995-04-26 | 1998-12-08 | Wink Communications, Inc. | Compact graphical interactive information system |
US5872928A (en) * | 1995-02-24 | 1999-02-16 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US5911143A (en) * | 1994-08-15 | 1999-06-08 | International Business Machines Corporation | Method and system for advanced role-based access control in distributed and centralized computer systems |
US5925126A (en) * | 1997-03-18 | 1999-07-20 | Memco Software, Ltd. | Method for security shield implementation in computer system's software |
US6052531A (en) * | 1998-03-25 | 2000-04-18 | Symantec Corporation | Multi-tiered incremental software updating |
US6055637A (en) * | 1996-09-27 | 2000-04-25 | Electronic Data Systems Corporation | System and method for accessing enterprise-wide resources by presenting to the resource a temporary credential |
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US6108699A (en) * | 1997-06-27 | 2000-08-22 | Sun Microsystems, Inc. | System and method for modifying membership in a clustered distributed computer system and updating system configuration |
US6151599A (en) * | 1998-07-17 | 2000-11-21 | International Business Machines Corporation | Web client scripting test architecture for web server-based authentication |
US6161139A (en) * | 1998-07-10 | 2000-12-12 | Encommerce, Inc. | Administrative roles that govern access to administrative functions |
US6182226B1 (en) * | 1998-03-18 | 2001-01-30 | Secure Computing Corporation | System and method for controlling interactions between networks |
US6202066B1 (en) * | 1997-11-19 | 2001-03-13 | The United States Of America As Represented By The Secretary Of Commerce | Implementation of role/group permission association using object access type |
US6226745B1 (en) * | 1997-03-21 | 2001-05-01 | Gio Wiederhold | Information sharing system and method with requester dependent sharing and security rules |
US20010047485A1 (en) * | 2000-03-06 | 2001-11-29 | Daniel Brown | Computer security system |
US6339423B1 (en) * | 1999-08-23 | 2002-01-15 | Entrust, Inc. | Multi-domain access control |
US6357010B1 (en) * | 1998-02-17 | 2002-03-12 | Secure Computing Corporation | System and method for controlling access to documents stored on an internal network |
US20020107913A1 (en) * | 2001-02-08 | 2002-08-08 | Rivera Gustavo R. | System and method for rendering documents in a user-familiar format |
US20020147801A1 (en) * | 2001-01-29 | 2002-10-10 | Gullotta Tony J. | System and method for provisioning resources to users based on policies, roles, organizational information, and attributes |
US20020178119A1 (en) * | 2001-05-24 | 2002-11-28 | International Business Machines Corporation | Method and system for a role-based access control model with active roles |
US20020188869A1 (en) * | 2001-06-11 | 2002-12-12 | Paul Patrick | System and method for server security and entitlement processing |
US20030046576A1 (en) * | 2001-08-30 | 2003-03-06 | International Business Machines Corporation | Role-permission model for security policy administration and enforcement |
US6574736B1 (en) * | 1998-11-30 | 2003-06-03 | Microsoft Corporation | Composable roles |
US6581054B1 (en) * | 1999-07-30 | 2003-06-17 | Computer Associates Think, Inc. | Dynamic query model and method |
US20030126464A1 (en) * | 2001-12-04 | 2003-07-03 | Mcdaniel Patrick D. | Method and system for determining and enforcing security policy in a communication session |
US20030126236A1 (en) * | 2001-12-05 | 2003-07-03 | Marl Dennis Craig | Configuration and management systems for mobile and embedded devices |
US6606708B1 (en) * | 1997-09-26 | 2003-08-12 | Worldcom, Inc. | Secure server architecture for Web based data management |
US6735624B1 (en) * | 2000-04-07 | 2004-05-11 | Danger, Inc. | Method for configuring and authenticating newly delivered portal device |
US6751657B1 (en) * | 1999-12-21 | 2004-06-15 | Worldcom, Inc. | System and method for notification subscription filtering based on user role |
US20040215650A1 (en) * | 2003-04-09 | 2004-10-28 | Ullattil Shaji | Interfaces and methods for group policy management |
US6886100B2 (en) * | 2001-05-15 | 2005-04-26 | Hewlett-Packard Development Company, L.P. | Disabling tool execution via roles |
US6957331B2 (en) * | 2000-01-14 | 2005-10-18 | International Business Machines Corporation | Method of achieving multiple processor agreement in asynchronous networks |
US6978379B1 (en) * | 1999-05-28 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Configuring computer systems |
US7089584B1 (en) * | 2000-05-24 | 2006-08-08 | Sun Microsystems, Inc. | Security architecture for integration of enterprise information system with J2EE platform |
US7093283B1 (en) * | 2002-02-15 | 2006-08-15 | Cisco Technology, Inc. | Method and apparatus for deploying configuration instructions to security devices in order to implement a security policy on a network |
US7185332B1 (en) * | 1998-03-25 | 2007-02-27 | Symantec Corporation | Multi-tiered incremental software updating |
US7185192B1 (en) * | 2000-07-07 | 2007-02-27 | Emc Corporation | Methods and apparatus for controlling access to a resource |
Family Cites Families (168)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1253438A (en) * | 1916-03-13 | 1918-01-15 | Charles E Stevens Jr | Recording-gage. |
US3748646A (en) * | 1971-06-08 | 1973-07-24 | Daktronics | Voting system |
US5173939A (en) | 1990-09-28 | 1992-12-22 | Digital Equipment Corporation | Access control subsystem and method for distributed computer system using compound principals |
US5426747A (en) | 1991-03-22 | 1995-06-20 | Object Design, Inc. | Method and apparatus for virtual memory mapping and transaction management in an object-oriented database system |
US5237614A (en) | 1991-06-07 | 1993-08-17 | Security Dynamics Technologies, Inc. | Integrated network security system |
US5347653A (en) | 1991-06-28 | 1994-09-13 | Digital Equipment Corporation | System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes |
US5481700A (en) * | 1991-09-27 | 1996-01-02 | The Mitre Corporation | Apparatus for design of a multilevel secure database management system based on a multilevel logic programming system |
US5355474A (en) | 1991-09-27 | 1994-10-11 | Thuraisngham Bhavani M | System for multilevel secure database management using a knowledge base with release-based and other security constraints for query, response and update modification |
US5557747A (en) | 1993-06-22 | 1996-09-17 | Rogers; Lawrence D. | Network policy implementation system for performing network control operations in response to changes in network state |
JPH0798669A (en) | 1993-08-05 | 1995-04-11 | Hitachi Ltd | Distributed data base management system |
US5400248A (en) * | 1993-09-15 | 1995-03-21 | John D. Chisholm | Computer network based conditional voting system |
US5544322A (en) | 1994-05-09 | 1996-08-06 | International Business Machines Corporation | System and method for policy-based inter-realm authentication within a distributed processing system |
US5627886A (en) * | 1994-09-22 | 1997-05-06 | Electronic Data Systems Corporation | System and method for detecting fraudulent network usage patterns using real-time network monitoring |
CA2683230C (en) * | 1995-02-13 | 2013-08-27 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
US5889953A (en) * | 1995-05-25 | 1999-03-30 | Cabletron Systems, Inc. | Policy management and conflict resolution in computer networks |
US5757669A (en) * | 1995-05-31 | 1998-05-26 | Netscape Communications Corporation | Method and apparatus for workgroup information replication |
DE69601149T2 (en) * | 1995-07-03 | 1999-08-05 | Sun Microsystems Inc | Systems and methods for implementing a hierarchical policy for the administration of a computer system |
US6026368A (en) * | 1995-07-17 | 2000-02-15 | 24/7 Media, Inc. | On-line interactive system and method for providing content and advertising information to a targeted set of viewers |
US5825883A (en) | 1995-10-31 | 1998-10-20 | Interval Systems, Inc. | Method and apparatus that accounts for usage of digital applications |
JP3023949B2 (en) * | 1995-12-12 | 2000-03-21 | 株式会社村田製作所 | Dielectric filter |
US5802276A (en) * | 1996-01-03 | 1998-09-01 | International Business Machines Corporation | Information handling system, method, and article of manufacture including a vault object for encapsulation of object security credentials |
US5826000A (en) | 1996-02-29 | 1998-10-20 | Sun Microsystems, Inc. | System and method for automatic configuration of home network computers |
US5826268A (en) | 1996-04-12 | 1998-10-20 | Ontos, Inc. | Secure multilevel object oriented database management system |
US5848396A (en) | 1996-04-26 | 1998-12-08 | Freedom Of Information, Inc. | Method and apparatus for determining behavioral profile of a computer user |
US6216231B1 (en) | 1996-04-30 | 2001-04-10 | At & T Corp. | Specifying security protocols and policy constraints in distributed systems |
US5987469A (en) | 1996-05-14 | 1999-11-16 | Micro Logic Corp. | Method and apparatus for graphically representing information stored in electronic media |
US5918210A (en) | 1996-06-07 | 1999-06-29 | Electronic Data Systems Corporation | Business query tool, using policy objects to provide query responses |
US5956400A (en) | 1996-07-19 | 1999-09-21 | Digicash Incorporated | Partitioned information storage systems with controlled retrieval |
US6052723A (en) * | 1996-07-25 | 2000-04-18 | Stockmaster.Com, Inc. | Method for aggregate control on an electronic network |
US6055515A (en) * | 1996-07-30 | 2000-04-25 | International Business Machines Corporation | Enhanced tree control system for navigating lattices data structures and displaying configurable lattice-node labels |
US5950195A (en) | 1996-09-18 | 1999-09-07 | Secure Computing Corporation | Generalized security policy management system and method |
US6029182A (en) * | 1996-10-04 | 2000-02-22 | Canon Information Systems, Inc. | System for generating a custom formatted hypertext document by using a personal profile to retrieve hierarchical documents |
US6154844A (en) | 1996-11-08 | 2000-11-28 | Finjan Software, Ltd. | System and method for attaching a downloadable security profile to a downloadable |
US6058392A (en) * | 1996-11-18 | 2000-05-02 | Wesley C. Sampson Revocable Trust | Method for the organizational indexing, storage, and retrieval of data according to data pattern signatures |
US6292900B1 (en) | 1996-12-18 | 2001-09-18 | Sun Microsystems, Inc. | Multilevel security attribute passing methods, apparatuses, and computer program products in a stream |
US5987611A (en) | 1996-12-31 | 1999-11-16 | Zone Labs, Inc. | System and methodology for managing internet access on a per application basis for client computers connected to the internet |
US6241608B1 (en) * | 1997-01-15 | 2001-06-05 | Lawrence J. Torango | Progressive wagering system |
US6466239B2 (en) | 1997-01-24 | 2002-10-15 | Sony Corporation | Method and apparatus for editing data used in creating a three-dimensional virtual reality environment |
US5867667A (en) | 1997-03-24 | 1999-02-02 | Pfn, Inc. | Publication network control system using domain and client side communications resource locator lists for managing information communications between the domain server and publication servers |
US6275941B1 (en) | 1997-03-28 | 2001-08-14 | Hiatchi, Ltd. | Security management method for network system |
US5991877A (en) | 1997-04-03 | 1999-11-23 | Lockheed Martin Corporation | Object-oriented trusted application framework |
US6185587B1 (en) * | 1997-06-19 | 2001-02-06 | International Business Machines Corporation | System and method for building a web site with automated help |
US6684369B1 (en) * | 1997-06-19 | 2004-01-27 | International Business Machines, Corporation | Web site creator using templates |
US6029144A (en) | 1997-08-29 | 2000-02-22 | International Business Machines Corporation | Compliance-to-policy detection method and system |
US6005571A (en) | 1997-09-30 | 1999-12-21 | Softline, Inc. | Graphical user interface for managing security in a database system |
US6006194A (en) | 1997-10-01 | 1999-12-21 | Merel; Peter A. | Computer-implemented system for controlling resources and policies |
US5954798A (en) | 1997-10-06 | 1999-09-21 | Ncr Corporation | Mechanism for dependably managing web synchronization and tracking operations among multiple browsers |
US6317868B1 (en) | 1997-10-24 | 2001-11-13 | University Of Washington | Process for transparently enforcing protection domains and access control as well as auditing operations in software components |
US6157924A (en) | 1997-11-07 | 2000-12-05 | Bell & Howell Mail Processing Systems Company | Systems, methods, and computer program products for delivering information in a preferred medium |
US6385627B1 (en) | 1997-11-24 | 2002-05-07 | International Business Machines Corporation | Method, apparatus and computer program product for providing document user role indication |
IL122314A (en) | 1997-11-27 | 2001-03-19 | Security 7 Software Ltd | Method and system for enforcing a communication security policy |
US5966707A (en) | 1997-12-02 | 1999-10-12 | International Business Machines Corporation | Method for managing a plurality of data processes residing in heterogeneous data repositories |
US6202157B1 (en) * | 1997-12-08 | 2001-03-13 | Entrust Technologies Limited | Computer network security system and method having unilateral enforceable security policy provision |
US6360363B1 (en) * | 1997-12-31 | 2002-03-19 | Eternal Systems, Inc. | Live upgrade process for object-oriented programs |
US6035423A (en) * | 1997-12-31 | 2000-03-07 | Network Associates, Inc. | Method and system for providing automated updating and upgrading of antivirus applications using a computer network |
US6202207B1 (en) * | 1998-01-28 | 2001-03-13 | International Business Machines Corporation | Method and a mechanism for synchronized updating of interoperating software |
CA2228687A1 (en) | 1998-02-04 | 1999-08-04 | Brett Howard | Secured virtual private networks |
US6484261B1 (en) | 1998-02-17 | 2002-11-19 | Cisco Technology, Inc. | Graphical network security policy management |
US6108687A (en) * | 1998-03-02 | 2000-08-22 | Hewlett Packard Company | System and method for providing a synchronized display to a plurality of computers over a global computer network |
US6304881B1 (en) * | 1998-03-03 | 2001-10-16 | Pumatech, Inc. | Remote data access and synchronization |
US6141686A (en) | 1998-03-13 | 2000-10-31 | 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 |
US6285985B1 (en) | 1998-04-03 | 2001-09-04 | Preview Systems, Inc. | Advertising-subsidized and advertising-enabled software |
US6295607B1 (en) | 1998-04-06 | 2001-09-25 | Bindview Development Corporation | System and method for security control in a data processing system |
US6182277B1 (en) * | 1998-04-15 | 2001-01-30 | Oracle Corporation | Methods and apparatus for declarative programming techniques in an object oriented environment |
US6339826B2 (en) | 1998-05-05 | 2002-01-15 | International Business Machines Corp. | Client-server system for maintaining a user desktop consistent with server application user access permissions |
US6148333A (en) | 1998-05-13 | 2000-11-14 | Mgi Software Corporation | Method and system for server access control and tracking |
US6122647A (en) | 1998-05-19 | 2000-09-19 | Perspecta, Inc. | Dynamic generation of contextual links in hypertext documents |
US6167407A (en) | 1998-06-03 | 2000-12-26 | Symantec Corporation | Backtracked incremental updating |
US6083276A (en) * | 1998-06-11 | 2000-07-04 | Corel, Inc. | Creating and configuring component-based applications using a text-based descriptive attribute grammar |
US6253321B1 (en) | 1998-06-19 | 2001-06-26 | Ssh Communications Security Ltd. | Method and arrangement for implementing IPSEC policy management using filter code |
US6285366B1 (en) | 1998-06-30 | 2001-09-04 | Sun Microsystems, Inc. | Hierarchy navigation system |
US6209101B1 (en) | 1998-07-17 | 2001-03-27 | Secure Computing Corporation | Adaptive security system having a hierarchy of security servers |
US6170009B1 (en) | 1998-07-17 | 2001-01-02 | Kallol Mandal | Controlling devices on a network through policies |
US6141010A (en) | 1998-07-17 | 2000-10-31 | B. E. Technology, Llc | Computer interface method and apparatus with targeted advertising |
AU5465099A (en) * | 1998-08-04 | 2000-02-28 | Rulespace, Inc. | Method and system for deriving computer users' personal interests |
US6397222B1 (en) * | 1998-08-07 | 2002-05-28 | Paul Zellweger | Method and apparatus for end-user management of a content menu on a network |
US6473791B1 (en) | 1998-08-17 | 2002-10-29 | Microsoft Corporation | Object load balancing |
US6397231B1 (en) * | 1998-08-31 | 2002-05-28 | Xerox Corporation | Virtual documents generated via combined documents or portions of documents retrieved from data repositories |
US6412070B1 (en) * | 1998-09-21 | 2002-06-25 | Microsoft Corporation | Extensible security system and method for controlling access to objects in a computing environment |
US6377973B2 (en) * | 1998-09-30 | 2002-04-23 | Emrys Technologies, Ltd. | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
US6341352B1 (en) | 1998-10-15 | 2002-01-22 | International Business Machines Corporation | Method for changing a security policy during processing of a transaction request |
US6477543B1 (en) | 1998-10-23 | 2002-11-05 | International Business Machines Corporation | Method, apparatus and program storage device for a client and adaptive synchronization and transformation server |
US6167445A (en) | 1998-10-26 | 2000-12-26 | Cisco Technology, Inc. | Method and apparatus for defining and implementing high-level quality of service policies in computer networks |
US6158010A (en) | 1998-10-28 | 2000-12-05 | Crosslogix, Inc. | System and method for maintaining security in a distributed computer network |
US6460141B1 (en) | 1998-10-28 | 2002-10-01 | Rsa Security Inc. | Security and access management system for web-enabled and non-web-enabled applications and content on a computer network |
JP3856969B2 (en) * | 1998-11-02 | 2006-12-13 | 株式会社日立製作所 | Object analysis design support method |
US6530024B1 (en) | 1998-11-20 | 2003-03-04 | Centrax Corporation | Adaptive feedback security system and method |
US6327618B1 (en) | 1998-12-03 | 2001-12-04 | Cisco Technology, Inc. | Recognizing and processing conflicts in network management policies |
US6301613B1 (en) | 1998-12-03 | 2001-10-09 | Cisco Technology, Inc. | Verifying that a network management policy used by a computer system can be satisfied and is feasible for use |
CA2292272A1 (en) * | 1998-12-22 | 2000-06-22 | Nortel Networks Corporation | System and method to support configurable policies for services in directory-based networks |
US6381579B1 (en) * | 1998-12-23 | 2002-04-30 | International Business Machines Corporation | System and method to provide secure navigation to resources on the internet |
US6393474B1 (en) | 1998-12-31 | 2002-05-21 | 3Com Corporation | Dynamic policy management apparatus and method using active network devices |
US6510513B1 (en) * | 1999-01-13 | 2003-01-21 | Microsoft Corporation | Security services and policy enforcement for electronic data |
US6412077B1 (en) | 1999-01-14 | 2002-06-25 | Cisco Technology, Inc. | Disconnect policy for distributed computing systems |
US6327594B1 (en) | 1999-01-29 | 2001-12-04 | International Business Machines Corporation | Methods for shared data management in a pervasive computing environment |
US6308163B1 (en) | 1999-03-16 | 2001-10-23 | Hewlett-Packard Company | System and method for enterprise workflow resource management |
US6260050B1 (en) * | 1999-03-23 | 2001-07-10 | Microstrategy, Inc. | System and method of adapting automatic output of service related OLAP reports to disparate output devices |
US6154766A (en) * | 1999-03-23 | 2000-11-28 | Microstrategy, Inc. | System and method for automatic transmission of personalized OLAP report output |
US6757698B2 (en) * | 1999-04-14 | 2004-06-29 | Iomega Corporation | Method and apparatus for automatically synchronizing data from a host computer to two or more backup data storage locations |
US20030069874A1 (en) * | 1999-05-05 | 2003-04-10 | Eyal Hertzog | Method and system to automate the updating of personal information within a personal information management application and to synchronize such updated personal information management applications |
US7472349B1 (en) * | 1999-06-01 | 2008-12-30 | Oracle International Corporation | Dynamic services infrastructure for allowing programmatic access to internet and other resources |
US6988138B1 (en) * | 1999-06-30 | 2006-01-17 | Blackboard Inc. | Internet-based education support system and methods |
US6769095B1 (en) * | 1999-07-23 | 2004-07-27 | Codagen Technologies Corp. | Hierarchically structured control information editor |
US6519647B1 (en) | 1999-07-23 | 2003-02-11 | Microsoft Corporation | Methods and apparatus for synchronizing access control in a web server |
US6587876B1 (en) * | 1999-08-24 | 2003-07-01 | Hewlett-Packard Development Company | Grouping targets of management policies |
US6934934B1 (en) * | 1999-08-30 | 2005-08-23 | Empirix Inc. | Method and system for software object testing |
US7051316B2 (en) * | 1999-10-05 | 2006-05-23 | Borland Software Corporation | Distributed computing component system with diagrammatic graphical representation of code with separate delineated display area by type |
US6430556B1 (en) * | 1999-11-01 | 2002-08-06 | Sun Microsystems, Inc. | System and method for providing a query object development environment |
US6865549B1 (en) * | 1999-11-15 | 2005-03-08 | Sun Microsystems, Inc. | Method and apparatus for concurrency control in a policy-based management system |
JP3963417B2 (en) * | 1999-11-19 | 2007-08-22 | 株式会社東芝 | Communication method and electronic device for data synchronization processing |
US6487594B1 (en) | 1999-11-30 | 2002-11-26 | Mediaone Group, Inc. | Policy management method and system for internet service providers |
US6418448B1 (en) | 1999-12-06 | 2002-07-09 | Shyam Sundar Sarkar | Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web |
US6587849B1 (en) * | 1999-12-10 | 2003-07-01 | Art Technology Group, Inc. | Method and system for constructing personalized result sets |
WO2001045018A1 (en) * | 1999-12-17 | 2001-06-21 | Dorado Network Systems Corporation | Purpose-based adaptive rendering |
US6584454B1 (en) * | 1999-12-31 | 2003-06-24 | Ge Medical Technology Services, Inc. | Method and apparatus for community management in remote system servicing |
US6633855B1 (en) * | 2000-01-06 | 2003-10-14 | International Business Machines Corporation | Method, system, and program for filtering content using neural networks |
US6484177B1 (en) | 2000-01-13 | 2002-11-19 | International Business Machines Corporation | Data management interoperability methods for heterogeneous directory structures |
EP1117220A1 (en) * | 2000-01-14 | 2001-07-18 | Sun Microsystems, Inc. | Method and system for protocol conversion |
US6694336B1 (en) * | 2000-01-25 | 2004-02-17 | Fusionone, Inc. | Data transfer and synchronization system |
US6735586B2 (en) * | 2000-02-08 | 2004-05-11 | Sybase, Inc. | System and method for dynamic content retrieval |
US6901403B1 (en) * | 2000-03-02 | 2005-05-31 | Quovadx, Inc. | XML presentation of general-purpose data sources |
WO2001075549A2 (en) * | 2000-03-30 | 2001-10-11 | Cygent, Inc. | System and method for establishing electronic business systems for supporting communications services commerce |
US6697805B1 (en) * | 2000-04-14 | 2004-02-24 | Microsoft Corporation | XML methods and systems for synchronizing multiple computing devices |
US20020103818A1 (en) * | 2000-05-04 | 2002-08-01 | Kirkfire, Inc. | Information repository system and method for an internet portal system |
US6327628B1 (en) * | 2000-05-19 | 2001-12-04 | Epicentric, Inc. | Portal server that provides a customizable user Interface for access to computer networks |
US7085994B2 (en) * | 2000-05-22 | 2006-08-01 | Sap Portals, Inc. | Snippet selection |
US20020019827A1 (en) * | 2000-06-05 | 2002-02-14 | Shiman Leon G. | Method and apparatus for managing documents in a centralized document repository system |
US6779002B1 (en) * | 2000-06-13 | 2004-08-17 | Sprint Communications Company L.P. | Computer software framework and method for synchronizing data across multiple databases |
US6785721B1 (en) * | 2000-06-19 | 2004-08-31 | International Business Machines Corporation | System and method for providing a distributable runtime that deploys web applications and services from a workflow, enterprise, and mail-enabled web application server and platform |
WO2002019097A1 (en) * | 2000-09-01 | 2002-03-07 | International Interactive Commerce, Ltd. | System and method for collaboration using web browsers |
US6477575B1 (en) | 2000-09-12 | 2002-11-05 | Capital One Financial Corporation | System and method for performing dynamic Web marketing and advertising |
US6581071B1 (en) * | 2000-09-12 | 2003-06-17 | Survivors Of The Shoah Visual History Foundation | Surveying system and method |
US6754672B1 (en) * | 2000-09-13 | 2004-06-22 | American Management Systems, Inc. | System and method for efficient integration of government administrative and program systems |
WO2002023368A1 (en) * | 2000-09-15 | 2002-03-21 | Wonderware Corporation | A method and system for administering a concurrent user licensing agreement on a manufacturing/process control information portal server |
US6856999B2 (en) * | 2000-10-02 | 2005-02-15 | Microsoft Corporation | Synchronizing a store with write generations |
US6912538B2 (en) * | 2000-10-20 | 2005-06-28 | Kevin Stapel | System and method for dynamic generation of structured documents |
US6970939B2 (en) * | 2000-10-26 | 2005-11-29 | Intel Corporation | Method and apparatus for large payload distribution in a network |
KR100398711B1 (en) * | 2000-11-08 | 2003-09-19 | 주식회사 와이즈엔진 | Content publication system for supporting real-time integration and processing of multimedia contents including dynamic data and method thereof |
US6889222B1 (en) * | 2000-12-26 | 2005-05-03 | Aspect Communications Corporation | Method and an apparatus for providing personalized service |
KR100393273B1 (en) * | 2001-02-12 | 2003-07-31 | (주)폴리픽스 | An Online Data Communicating System and a Method in a Private Network |
US6985915B2 (en) * | 2001-02-28 | 2006-01-10 | Kiran Somalwar | Application independent write monitoring method for fast backup and synchronization of files |
WO2002076077A1 (en) * | 2001-03-16 | 2002-09-26 | Leap Wireless International, Inc. | Method and system for distributing content over a wireless communications system |
US7080000B1 (en) * | 2001-03-30 | 2006-07-18 | Mcafee, Inc. | Method and system for bi-directional updating of antivirus database |
US7003578B2 (en) * | 2001-04-26 | 2006-02-21 | Hewlett-Packard Development Company, L.P. | Method and system for controlling a policy-based network |
US7047522B1 (en) * | 2001-04-30 | 2006-05-16 | General Electric Capital Corporation | Method and system for verifying a computer program |
US20020169893A1 (en) * | 2001-05-09 | 2002-11-14 | Li-Han Chen | System and method for computer data synchronization |
WO2003009177A1 (en) * | 2001-07-16 | 2003-01-30 | Dh Labs, Inc. | Web site application development method using object model for managing web-based content |
US6922695B2 (en) * | 2001-09-06 | 2005-07-26 | Initiate Systems, Inc. | System and method for dynamically securing dynamic-multi-sourced persisted EJBS |
US20030146937A1 (en) * | 2001-09-11 | 2003-08-07 | Lee Seung Woo | Multi-level data management system |
CA2460332A1 (en) * | 2001-09-12 | 2003-04-10 | Opentv, Inc. | A method and apparatus for disconnected chat room lurking in an interactive television environment |
US7035944B2 (en) * | 2001-09-19 | 2006-04-25 | International Business Machines Corporation | Programmatic management of software resources in a content framework environment |
US7765484B2 (en) * | 2001-09-28 | 2010-07-27 | Aol Inc. | Passive personalization of lists |
US7496645B2 (en) * | 2001-10-18 | 2009-02-24 | Hewlett-Packard Development Company, L.P. | Deployment of business logic software and data content onto network servers |
WO2003036500A1 (en) * | 2001-10-24 | 2003-05-01 | Bea Systems, Inc. | System and method for application flow integration in a portal framework |
US6918088B2 (en) * | 2001-11-05 | 2005-07-12 | Sun Microsystems, Inc. | Service portal with application framework for facilitating application and feature development |
US7054910B1 (en) * | 2001-12-20 | 2006-05-30 | Emc Corporation | Data replication facility for distributed computing environments |
AU2002359821A1 (en) * | 2001-12-21 | 2003-07-15 | Xmlcities, Inc. | Extensible stylesheet designs using meta-tag and/or associated meta-tag information |
US7062511B1 (en) * | 2001-12-31 | 2006-06-13 | Oracle International Corporation | Method and system for portal web site generation |
US7565367B2 (en) * | 2002-01-15 | 2009-07-21 | Iac Search & Media, Inc. | Enhanced popularity ranking |
US20040078371A1 (en) * | 2002-05-22 | 2004-04-22 | Joel Worrall | Method and system for providing multiple virtual portals on a computer network |
US7302488B2 (en) * | 2002-06-28 | 2007-11-27 | Microsoft Corporation | Parental controls customization and notification |
US8631142B2 (en) * | 2002-08-07 | 2014-01-14 | International Business Machines Corporation | Inserting targeted content into a portlet content stream |
US20040098467A1 (en) * | 2002-11-15 | 2004-05-20 | Humanizing Technologies, Inc. | Methods and systems for implementing a customized life portal |
US7035879B2 (en) * | 2002-12-26 | 2006-04-25 | Hon Hai Precision Ind. Co., Ltd. | System and method for synchronizing data of wireless devices |
US20040167880A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | System and method for searching a virtual repository content |
WO2004107112A2 (en) * | 2003-05-23 | 2004-12-09 | Snapbridge Software, Inc. | Data federation methods and system |
US7552109B2 (en) * | 2003-10-15 | 2009-06-23 | International Business Machines Corporation | System, method, and service for collaborative focused crawling of documents on a network |
US7953734B2 (en) * | 2005-09-26 | 2011-05-31 | Oracle International Corporation | System and method for providing SPI extensions for content management system |
-
2001
- 2001-06-11 US US09/878,536 patent/US7392546B2/en not_active Expired - Lifetime
-
2002
- 2002-05-29 WO PCT/US2002/016644 patent/WO2002101973A1/en active Application Filing
- 2002-05-29 CN CNB028148207A patent/CN100361435C/en not_active Expired - Lifetime
- 2002-05-29 AU AU2002310144A patent/AU2002310144B2/en not_active Expired
- 2002-05-29 JP JP2003504584A patent/JP2004533075A/en active Pending
- 2002-05-29 EP EP02737197.0A patent/EP1405457B1/en not_active Expired - Lifetime
-
2007
- 2007-03-14 US US11/686,218 patent/US20070157297A1/en not_active Abandoned
-
2008
- 2008-06-19 US US12/142,451 patent/US7823189B2/en not_active Expired - Fee Related
Patent Citations (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5551040A (en) * | 1993-06-02 | 1996-08-27 | Lucent Technologies Inc. | Methods and apparatus for specifying the contexts of names in callback-style programming |
US5369702A (en) * | 1993-10-18 | 1994-11-29 | Tecsec Incorporated | Distributed cryptographic object method |
US5911143A (en) * | 1994-08-15 | 1999-06-08 | International Business Machines Corporation | Method and system for advanced role-based access control in distributed and centralized computer systems |
US5872928A (en) * | 1995-02-24 | 1999-02-16 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US6243747B1 (en) * | 1995-02-24 | 2001-06-05 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
US5848352A (en) * | 1995-04-26 | 1998-12-08 | Wink Communications, Inc. | Compact graphical interactive information system |
US5764958A (en) * | 1995-11-30 | 1998-06-09 | International Business Machines Corporation | Method and apparatus for creating dynamic roles with a system object model |
US6055637A (en) * | 1996-09-27 | 2000-04-25 | Electronic Data Systems Corporation | System and method for accessing enterprise-wide resources by presenting to the resource a temporary credential |
US5925126A (en) * | 1997-03-18 | 1999-07-20 | Memco Software, Ltd. | Method for security shield implementation in computer system's software |
US6226745B1 (en) * | 1997-03-21 | 2001-05-01 | Gio Wiederhold | Information sharing system and method with requester dependent sharing and security rules |
US6108699A (en) * | 1997-06-27 | 2000-08-22 | Sun Microsystems, Inc. | System and method for modifying membership in a clustered distributed computer system and updating system configuration |
US6606708B1 (en) * | 1997-09-26 | 2003-08-12 | Worldcom, Inc. | Secure server architecture for Web based data management |
US6202066B1 (en) * | 1997-11-19 | 2001-03-13 | The United States Of America As Represented By The Secretary Of Commerce | Implementation of role/group permission association using object access type |
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US6357010B1 (en) * | 1998-02-17 | 2002-03-12 | Secure Computing Corporation | System and method for controlling access to documents stored on an internal network |
US6182226B1 (en) * | 1998-03-18 | 2001-01-30 | Secure Computing Corporation | System and method for controlling interactions between networks |
US6651249B2 (en) * | 1998-03-25 | 2003-11-18 | Symantec Corporation | Multi-tiered incremental software updating |
US7185332B1 (en) * | 1998-03-25 | 2007-02-27 | Symantec Corporation | Multi-tiered incremental software updating |
US6052531A (en) * | 1998-03-25 | 2000-04-18 | Symantec Corporation | Multi-tiered incremental software updating |
US6161139A (en) * | 1998-07-10 | 2000-12-12 | Encommerce, Inc. | Administrative roles that govern access to administrative functions |
US6151599A (en) * | 1998-07-17 | 2000-11-21 | International Business Machines Corporation | Web client scripting test architecture for web server-based authentication |
US6574736B1 (en) * | 1998-11-30 | 2003-06-03 | Microsoft Corporation | Composable roles |
US6978379B1 (en) * | 1999-05-28 | 2005-12-20 | Hewlett-Packard Development Company, L.P. | Configuring computer systems |
US6581054B1 (en) * | 1999-07-30 | 2003-06-17 | Computer Associates Think, Inc. | Dynamic query model and method |
US6339423B1 (en) * | 1999-08-23 | 2002-01-15 | Entrust, Inc. | Multi-domain access control |
US6751657B1 (en) * | 1999-12-21 | 2004-06-15 | Worldcom, Inc. | System and method for notification subscription filtering based on user role |
US6957331B2 (en) * | 2000-01-14 | 2005-10-18 | International Business Machines Corporation | Method of achieving multiple processor agreement in asynchronous networks |
US20010047485A1 (en) * | 2000-03-06 | 2001-11-29 | Daniel Brown | Computer security system |
US6735624B1 (en) * | 2000-04-07 | 2004-05-11 | Danger, Inc. | Method for configuring and authenticating newly delivered portal device |
US7089584B1 (en) * | 2000-05-24 | 2006-08-08 | Sun Microsystems, Inc. | Security architecture for integration of enterprise information system with J2EE platform |
US7185192B1 (en) * | 2000-07-07 | 2007-02-27 | Emc Corporation | Methods and apparatus for controlling access to a resource |
US20020147801A1 (en) * | 2001-01-29 | 2002-10-10 | Gullotta Tony J. | System and method for provisioning resources to users based on policies, roles, organizational information, and attributes |
US20020107913A1 (en) * | 2001-02-08 | 2002-08-08 | Rivera Gustavo R. | System and method for rendering documents in a user-familiar format |
US6886100B2 (en) * | 2001-05-15 | 2005-04-26 | Hewlett-Packard Development Company, L.P. | Disabling tool execution via roles |
US20020178119A1 (en) * | 2001-05-24 | 2002-11-28 | International Business Machines Corporation | Method and system for a role-based access control model with active roles |
US20020188869A1 (en) * | 2001-06-11 | 2002-12-12 | Paul Patrick | System and method for server security and entitlement processing |
US20030046576A1 (en) * | 2001-08-30 | 2003-03-06 | International Business Machines Corporation | Role-permission model for security policy administration and enforcement |
US20030126464A1 (en) * | 2001-12-04 | 2003-07-03 | Mcdaniel Patrick D. | Method and system for determining and enforcing security policy in a communication session |
US20030126236A1 (en) * | 2001-12-05 | 2003-07-03 | Marl Dennis Craig | Configuration and management systems for mobile and embedded devices |
US7219140B2 (en) * | 2001-12-05 | 2007-05-15 | Dennis Craig Marl | Configuration and management systems for mobile and embedded devices |
US7093283B1 (en) * | 2002-02-15 | 2006-08-15 | Cisco Technology, Inc. | Method and apparatus for deploying configuration instructions to security devices in order to implement a security policy on a network |
US20040215650A1 (en) * | 2003-04-09 | 2004-10-28 | Ullattil Shaji | Interfaces and methods for group policy management |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040019804A1 (en) * | 2002-07-24 | 2004-01-29 | Sun Microsystems, Inc. | System and method for processing callback requests included in web-based procedure calls through a firewall |
US7526797B2 (en) * | 2002-07-24 | 2009-04-28 | Sun Microsystems, Inc. | System and method for processing callback requests included in web-based procedure calls through a firewall |
US20050237996A1 (en) * | 2004-04-21 | 2005-10-27 | Yokogawa Electric Corporation | Electronic apparatus system and data control apparatus |
US20060236380A1 (en) * | 2005-03-22 | 2006-10-19 | Dell Products L.P. | System and method for grouping device or application objects in a directory service |
US7555771B2 (en) * | 2005-03-22 | 2009-06-30 | Dell Products L.P. | System and method for grouping device or application objects in a directory service |
US8156516B2 (en) | 2007-03-29 | 2012-04-10 | Emc Corporation | Virtualized federated role provisioning |
US20080244688A1 (en) * | 2007-03-29 | 2008-10-02 | Mcclain Carolyn B | Virtualized federated role provisioning |
US20080244687A1 (en) * | 2007-03-29 | 2008-10-02 | Mcclain Carolyn B | Federated role provisioning |
US9473499B2 (en) | 2007-03-29 | 2016-10-18 | Apple Inc. | Federated role provisioning |
US8719894B2 (en) * | 2007-03-29 | 2014-05-06 | Apple Inc. | Federated role provisioning |
US20080256643A1 (en) * | 2007-04-13 | 2008-10-16 | Microsoft Corporation | Multiple entity authorization model |
US8327456B2 (en) | 2007-04-13 | 2012-12-04 | Microsoft Corporation | Multiple entity authorization model |
US7992198B2 (en) * | 2007-04-13 | 2011-08-02 | Microsoft Corporation | Unified authentication for web method platforms |
US20080256616A1 (en) * | 2007-04-13 | 2008-10-16 | Microsoft Corporation | Unified authentication for web method platforms |
US20100218238A1 (en) * | 2009-02-26 | 2010-08-26 | Genpact Global Holdings (Bermuda) Limited | Method and system for access control by using an advanced command interface server |
US8856881B2 (en) * | 2009-02-26 | 2014-10-07 | Genpact Global Holdings (Bermuda) Ltd. | Method and system for access control by using an advanced command interface server |
US20210182428A1 (en) * | 2009-07-01 | 2021-06-17 | Vigilytics LLC | Using de-identified healthcare data to evaluate post-healthcare facility encounter treatment outcomes |
US11688015B2 (en) * | 2009-07-01 | 2023-06-27 | Vigilytics LLC | Using de-identified healthcare data to evaluate post-healthcare facility encounter treatment outcomes |
US10886012B1 (en) | 2009-07-01 | 2021-01-05 | Vigilytics LLC | De-identifying medical history information for medical underwriting |
US10943028B1 (en) * | 2009-07-01 | 2021-03-09 | Vigilytics LLC | Using de-identified healthcare data to evaluate post-healthcare facility encounter treatment outcomes |
US10068102B2 (en) | 2010-06-28 | 2018-09-04 | International Business Machines Corporation | Dynamic, temporary data access token |
CN102694787A (en) * | 2011-03-22 | 2012-09-26 | 中华电信股份有限公司 | Authorization information exchange method |
TWI419004B (en) * | 2011-03-22 | 2013-12-11 | Chunghwa Telecom Co Ltd | Information exchange authorization method |
US8874909B2 (en) | 2012-02-03 | 2014-10-28 | Daniel Joseph Lutz | System and method of storing data |
US10205786B2 (en) | 2016-04-22 | 2019-02-12 | Microsoft Technology Licensing, Llc | Multi-user application executing in user privilege mode |
Also Published As
Publication number | Publication date |
---|---|
EP1405457A4 (en) | 2010-07-07 |
US20080256610A1 (en) | 2008-10-16 |
US7823189B2 (en) | 2010-10-26 |
JP2004533075A (en) | 2004-10-28 |
US7392546B2 (en) | 2008-06-24 |
AU2002310144B2 (en) | 2007-09-06 |
EP1405457A1 (en) | 2004-04-07 |
US20020188869A1 (en) | 2002-12-12 |
CN100361435C (en) | 2008-01-09 |
WO2002101973A1 (en) | 2002-12-19 |
CN1535515A (en) | 2004-10-06 |
EP1405457B1 (en) | 2020-03-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7392546B2 (en) | System and method for server security and entitlement processing | |
AU2002310144A1 (en) | System and method for server security and entitlement processing | |
US7546462B2 (en) | Systems and methods for integration adapter security | |
Chadwick | Federated identity management | |
EP2689372B1 (en) | User to user delegation service in a federated identity management environment | |
US8327451B2 (en) | Secure system and method for enforcement of privacy policy and protection of confidentiality | |
EP1436682B1 (en) | System and method for specifying security, privacy, and access control to information used by others | |
US7356692B2 (en) | Method and system for enforcing access to a computing resource using a licensing attribute certificate | |
US20030229812A1 (en) | Authorization mechanism | |
Kraft | Designing a distributed access control processor for network services on the web | |
Chandersekaran et al. | Claims-based enterprise-wide access control | |
Zhang et al. | Achieving fine‐grained access control in virtual organizations | |
Marillonnet | User centric personal data management | |
Lu | User-to-user delegation in a federated identity environment' | |
Georgieva et al. | Security as a service model in SOA | |
Samson | Alternative Java Security Policy Model | |
Series | IBM WebSphere V5. 0 Security | |
Au | Agent-based one-shot authorisation scheme in a commercial extranet environment | |
Tu | A Preliminary Security Analysis of New Zealand's Igovt System | |
Šebök | Realization of the system for access management and identity federation with use of service mojeID and the product DirX Access. | |
Arribas | Access Control and Mobile Agents | |
Goovaerts et al. | Security services in mainstream enterprise-oriented middleware Platforms | |
Casassa-Mont | Architecture V2 Author: WP 14.2 Editor: Marco Casassa-Mont, Stefano Crosta, Thomas Kriegelstein, Dieter Sommer Reviewers | |
Fritsch | Towards Secure Electronic Workflows Examples of Applied PKI |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |