Description AN APPARATUS, COMPUTER-READABLE MEMORY AND METHOD FOR AUTHENTICATING AND AUTHORIZING A SERVICE REQUEST SENT FROM A SERVICE CLIENT TO A SERVICE PROVIDER Technical Field
[001] The present invention relates in general to network security, and, in particular, to authentication and authorization for services delivered over a network. Background Art
[002] For many years, network technology has enabled the sharing of, and remote access to, computing resources around the world. One computer can readily exchange data with a computer down the hall or in another country. Of course, it did not take long for the business world to harness the power of global networks, and network technology has fueled the growth of an entire new industry focused on delivering services across these networks.
[003] Commonly referred to as "web services," "application services," or "web service applications," network services typically expose existing business functionality over networks in a controlled environment and allow multiple applications to interact with each orther. Web service applications use standards such as Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), and Hypertext Transfer Protocol (HTTP) that are widely available and accepted to facilitate interaction across networks. XML provides a language to tag data so that the various components of a web service application can understand the request. SOAP is a method of packaging data before transmitting it across a network. HTTP is a transport protocol that delivers data across the network. Web service applications usually run in the background and do not have a graphical user interface (GUI). Rather, web services interact via a service program interface (SPI). An SPI is defined strictly in terms of the messages that the web service accepts. Thus, a typical web service invocation consists of a first application (hereinafter referred to as the "service client") sending an XML message, which is packaged in a SOAP "envelope," across the network via HTTP to a second application (hereinafter referred to as the "service provider"). The format of the XML message, of course, must comply with the requirements of the service provider's SPI. Web service applications can perform a wide variety of functions, ranging from simple stock quote requests to complicated billing processes. A web service invocation has many common names, including a "service request," a "request call," or just a "call."
For the sake of simplicity and clarity, any communication between a service client and a service provider for invoking a service will be referred to here as a "service request."
[004] Generally, a business needs to control access to web services to maximize profit and to protect internal computing resources. In general, a business achieves control by requiring service requests to pass through a web service manager, which acts much like a firewall. A web service manager controls access on two levels: the service client level and the service agreement level. To gain access to the desired web service, a service client must first present credentials to the web service manager. The web service manager then must determine whether the credentials are authentic. If the credentials are authentic, the web service manager then determines whether the service client is entitled to receive the service that the service client requested. Finally, if the credentials are authentic and the service client is authorized to access the service provider, the web service manager authorizes the service provider to process the request.
[005] Several methods of authentication are known in the art. The most conventional method requires each client to have a unique identifier (ID) and a password that only the client knows. Every time a client needs to access a service, the client must present an ID and a password that the network service provider can match to the ID presented. Naturally, both the client and the network service provider must keep the password from being unduly disclosed or otherwise disseminated. Passwords must also be difficult to guess. To make passwords difficult to guess, many businesses implement complex security policies that require passwords to meet strict criteria and require clients to change passwords frequently.
[006] Proprietary authentication methods, such as IBM' s WEB IDENTITY or TIVOLI ACCESS MANAGER, can also be used to control access to network services, but these methods are highly complex and require significant overhead.
[007] Digital certificates are another alternative to the ID/password approach. Digital certificates are generally issued by a certification authority, which is typically a trusted third-party organization or company. Alternatively, digital certificates can be "self-signed." A self-signed certificate is created by the holder of the certificate, but is still useful if the parties to a transaction are already familiar with each other and the integrity of the certificate is initially verified manually. A digital certificate is usually encrypted, and usually contains a holder's name or identifier, a serial number, and expiration date. X.509 is the most common digital certificate format, and is the format recommended by the International Telecommunications Union. The holder's name or identifier is commonly represented as a Distinguished Name, which is a part of the X.500 standard (also promulgated by ITU). A Distinguished Name is comprised of a combination of other X.500 identifiers, which may include a Common Name, an Orga-
nizational Unit, Organization, and Country.
[008] Digital certificates obviate the need for passwords and provide significant advantages over the use of IDs and passwords. An obvious advantage is that users do not have to conjure up or remember complicated passwords. Furthermore, digital certificates obviate the need to implement complicated security policies to ensure that passwords are difficult to guess, and they reduce the risk of security compromise through lost or exposed passwords.
[009] Although the art of using digital certificates is not new, integrating digital certificate technology into existing technologies, particularly web service applications, is extremely challenging. In particular, many existing web service applications have been designed to authenticate users based on an ID that is typically embedded in the service request. Thus, existing web service applications do not generally recognize IDs that are encoded in a digital certificate. Therefore, a need exists for an authentication mechanism that can be integrated with existing web services technology while reaping the benefits of digital certificate technology.
[010] Another problem that has arisen in the web services context is the malicious access and searching of databases. Typically, a malicious party is able to breach a firewall using access codes and other information which they are not authorized to use. In some circumstances, the malicious party has limited access within the firewall and attempts to access data repositories that he is not authorized to access. Once inside the firewall, the malicious party can search databases, hashtables, and other data structures at will because there are no further security features on the data structures. Such unauthorized access is not preferable. Consequently, a need exists for a security feature that will prevent a malicious party from searching a data repository when the malicious party gains access past the firewall. Disclosure of Invention
[011] According to a first aspect, there is provided a programmable apparatus for authenticating and authorizing a service request sent from a service client to a service provider, comprising: a processor; a memory connected to the processor; an authorization database in the memory; a service request filter program in the memory directing the processor to perform steps comprising: receive an incoming service request from the service client on a communication channel, the service request having a digital certificate attached; extract a client identifier from the digital certificate associated with the service request; store the client identifier in the memory using a security program; and wherein the security program encrypts the client identifier in a secure data structure using a key.
[012] In one embodiment, the security program comprises instructions for the processor
to perform steps further comprising: obtain a web context for the service request; get a requested object; obtain a SSL client certificate from the object; notify an authenticating and authorizing agent to continue processing the service request; and wherein the client certificate comprises the client identifier.
[013] In one embodiment the key is unique to the client identifier.
[014] In one embodiment the apparatus is further operable to send the service request on the communication channel to a web service manager and comprises a service client authentication program in the memory directing the processor to perform steps comprising: responsive to receiving an authentication request from a web service manager, request a client identifier; and wherein the client identifier is provided by the security program only if the key is presented with the request.
[015] In one embodiment the service client authentication program in the memory directs the processor to perform steps further comprising: match the client identifier with a service client record in the authorization database having the same client identifier; and responsive to matching the client identifier with a record in the authorization database, call a service authorization program in the memory; wherein the service authorization program directs the processor to perform steps comprising: determine if the client identifier associated with the service request is authorized to access the service provider; and responsive to determining that the service request is authorized, authorize the service provider to process the request.
[016] In one embodiment the service.request filter program further directs the processor to authenticate the digital certificate with the issuing certification authority.
[017] In one embodiment the digital certificate is an X.509 digital certificate.
[018] In one embodiment the client identifier is a distinguished name.
[019] In one embodiment the digital certificate is self-signed.
[020] In one embodiment the programmable apparatus further comprises an authorization log.
[021] In one embodiment the service client authentication program further records the client identifier in the authorization log.
[022] In one embodiment the service authorization program further records the client identifier and service request in the authorization log.
[023] In one embodiment the service request filter program in the memory is further operable to direct the processor to send the service request on the communication channel to a web service manager.
[024] In one embodiment, the client certificate comprises the client identifier, the apparatus further comprising; means for sending the service request to a web service manager; responsive to receiving an authentication request from a web service manager, means for requesting a client identifier; wherein the client identifier is
provided by the security program only if a key corresponding to the key is presented with the request; means for matching the client identifier with a service client record in the authorization database having the same client identifier; means for determining if the client identifier associated with the service request is authorized to access the service provider; responsive to determining that the service request is authorized, means for authorizing the service provider to process the request; means for authenticating the digital certificate with the issuing certification authority; wherein the digital certificate is an X.509 digital certificate; wherein the client identifier is a distinguished name; wherein the digital certificate is self-signed; means for recording the client identifier in an authorization log; and means for recording the client identifier and service request in the authorization log.
[025] The invention may be implemented as part of a web services architecture.
[026] According to a second aspect, there is provided a security program for encrypting a client identifier in a secured data structure, the security program comprising: a computer readable medium; wherein the computer readable medium comprises instructions for a processor to perform steps comprising: acquire a service request; extract the client identifier from the service request; store the client identifier in the secured data structure; and encrypt the secured data structure using a key.
[027] In one embodiment, the computer readable medium comprises further instructions for a process to perform steps comprising: obtain a web context for the service request; get a requested object; obtain a SSL client certificate from the object; notify an authenticating and authorizing agent to continue processing the service request; and wherein the client certificate comprises the client identifier.
[028] In one embodiment, the key is unique to the client identifier.
[029] According to another aspect, there is provided a computer-readable memory for causing a computer to authenticate and authorize service requests sent from a service client to a service provider, comprising: a computer-readable storage medium; an authorization database stored in the storage medium; a service request filter program stored in the storage medium, wherein the storage medium, so configured by the service request filter program, causes the computer to perform steps comprising: receive an incoming service request on a communication channel, the service request having a digital certificate attached; extract a client identifier from the digital certificate associated with the service request; store the client identifier in the memory using a security program; wherein the security program encrypts the client identifier in a secure data structure using a key; and send the service request on the communication channel to a web service manager.
[030] In one embodiment the security program comprises instructions for the processor to perform steps comprising: acquire a service request; extract the client identifier from
the service request; store the client identifier in the secured data structure; and encrypt the secured data structure using a key.
[031] In one embodiment the security program comprises instructions for the processor to perform steps further comprising: obtain a web context for the service request; get a requested object; obtain a SSL client certificate from the object; notify an au fhenticating and authorizing agent to continue processing the service request; and wherein the client certificate comprises the client identifier.
[032] In one embodiment the key is unique to the client identifier.
[033] In one embodiment, the security program comprises instructions for the processor to perform steps comprising: send the service request on the communication channel to a web service manager; wherein the computer readable memory further comprises a service client authentication program in the memory directing the processor to perform steps comprising: responsive to receiving an authentication request from a web service manager, request a client identifier; and wherein the client identifier is provided by the security program only if the key is presented with the request.
[034] In one embodiment, the service client authentication program in the memory directs the processor to perform steps further comprising: a service client authentication program stored in the storage medium, wherein the storage medium, so configured by the service client authentication program, causes the computer to perform steps comprising: responsive to receiving an authentication request from a web service manager, request a client identifier; wherein the client identifier is provided by the security program only if a key corresponding to the key is presented with the request; match the client identifier with a service client record in the authorization database having the same client identifier; responsive to matching the client identifier with a record in the authorization database, call a service authorization program in the memory; wherein the service authorization program is stored in the storage medium, and the storage medium, so configured by the service authorization program, causes the computer to perform steps comprising: determine if the client identifier associated with the service request is authorized to access the service provider; and responsive to determining that the service request is authorized, authorize the service provider to process the request.
[035] In one embodiment, the service request filter program further causes the computer to authenticate the digital certificate with the issuing certification authority.
[036] In one embodiment the digital certificate is an X.509 digital certificate.
[037] In one embodiment, the client identifier is a distinguished name.
[038] In one embodiment the digital certificate is self-signed.
[039] In one embodiment, the computer-readable memory further comprises an authorization log.
[040] In one embodiment, the service client authentication program further causes to the computer to record the client identifier in the authorization log.
[041] In one embodiment, the service authorization program further causes the computer to record the client identifier and service request in the authorization log.
[042] According to another aspect, there is provided an apparatus for authenticating and authorizing a service request sent from a service client to a service provider, comprising: means for receiving an incoming service request on a communication channel, the service request having a digital certificate attached; means for extracting a client identifier from the digital certificate associated with the service request; means for storing the client identifier in the memory using a security program; wherein the security program comprises: means for acquiring a service request; means for extracting the client identifier from the service request; means for storing the client identifier in the secured data structure; and means for encrypting the secured data structure using a key, wherein the client certificate comprises the client identifier; means for sending the service request to a web service manager; responsive to receiving an authentication request from a web service manager, means for requesting a client identifier; wherein the client identifier is provided by the security program only if a key corresponding to the key is presented with the request; means for matching the client identifier with a service client record in the authorization database having the same client identifier; means for determining if the client identifier associated with the service request is authorized to access the service provider;, responsive to determining that the service request is authorized, means for authorizing the service provider to process the request; means for authenticating the digital certificate with the issuing certification authority; wherein the digital certificate is an X.509 digital certificate; wherein the client identifier is a distinguished name; wherein the digital certificate is self-signed; means for recording the client identifier in an authorization log; and means for recording the client identifier and service request in the authorization log.
[043] According to another aspect, there is provided a method comprising the steps of: receiving an incoming service request from the service client on a communication channel, the service request having a digital certificate attached; extracting a client identifier from the digital certificate associated with the service request; storing the client identifier in the memory using a security program; and wherein the security program encrypts the client identifier in a secure data structure using a key.
[044] According to another aspect, there is provided a method for encrypting a client identifier in a secured data structure, the method comprising: acquiring a service request; extracting the client identifier from the service request; storing the client identifier in the secured data structure; and encrypting the secured data structure using a key.
[045] The invention may be implemented in computer software.
[046] There is preferably provided an architecture and design for central authentication and authorization in an on-demand utility environment using a secured global hashtable.
[047] The invention described herein comprises, in accordance with a preferred embodiment a Centralized Authentication & Authorization system (CAA). The CAA preferably facilitates secure communication between web service applications by maintaining an authorization database and providing authentication services to other web service applications.
[048] CAA preferably comprises a Service Request Filter (SRF), a Service Client Authentication Program (SCAP), a Service Authorization Program (SAP), an Authorization Database (ADB), and a Security Program (SP). The SRF preferably intercepts incoming service requests, extracts the service client's identifier from a digital certificate attached to the request, stores the identifier in a secured hashtable that is accessible only by web service applications, and forwards the service request on its original route. The SP preferably controls access to the secured hashtable by encrypting the secured hashtable using a key. Typically, a web service manager will receive the original request and invoke the SCAP. The SCAP matches the identifier with an identifier stored in the ADB and validates the service client. The SAP then preferably queries the ADB to determine if the service request is valid for the service ., client. If the service request is valid, the SAP preferably authorizes, the service request and the appropriate service provider processes the service request. In accordance with a preferred embodiment, the web service manager must present the correct key to the SP in order to access the client identifier and process the service request. Brief Description of the Drawings
[049] A preferred embodiment of the present invention will now be described, by way of example only, and with reference to the following drawings in which like reference numbers represent like parts of the preferred embodiment:
[050] Fig. 1 is a depiction of a typical networked computing environment in which the integrated server architecture could be implemented in accordance with a preferred embodiment;
[051] FIG. 2 represents the memory configuration of a typical computing workstation using the integrated server architecture of the preferred embodiment;
[052] FIG. 3 is a depiction of the logical design of a preferred embodiment of the present invention; and
[053] FIG. 4is an illustration of the logic of the Security Program (SP) of a preferred embodiment of the present invention.
Mode for the Invention
[054] A preferred embodiment of the present invention will now be described, by way of example only, and with reference to the following drawings in which like reference numbers represent like parts of the preferred embodiment: [055] Fig. 1 is a depiction of a typical networked computing environment in which the integrated server architecture could be implemented in accordance with a preferred embodiment; [056] FIG. 2 represents the memory configuration of a typical computing workstation using the integrated server architecture of the preferred embodiment; [057] FIG. 3 is a depiction of the logical design of a preferred embodiment of the present invention; and [058] FIG. 4is an illustration of the logic of the Security Program (SP) of a preferred embodiment of the present invention.