Patent Application
20250227102
The present invention relates to a computer program product, system, and method for an authenticator to communicate with a client computer to authenticate access to a server.
Servers connected to a network, such as the Internet, are vulnerable to attacks from remote users. If a server is vulnerable to attack or a request to the server contains malicious payload, then the server can be compromised leading to any number of security issues. Some web servers provide an authentication mechanism, for example a login to a web page, before further access to the server resources is permitted. This login can be part of the web server or application mechanism or within a web page or application.
Firewalls can also protect a server from malicious users. If the sources of a request are known, such as on an allow list, then the firewall may allow the requests while blocking connections from sources not indicted on the allow list. Another option is to block requests from Internet Protocol (IP) addresses associated with a geographic region. Another existing firewall solution is known as “captive portal”. In this instance, the firewall authenticates the request before the connection is established and the request is forwarded to the server.
Provided are a computer program product, system, and method for an authenticator to communicate with a client computer to authenticate access to a server. Authentication parameters are received to authenticate the client computer with the server, wherein the authentication parameters are for a domain name record for the server. The authentication parameters from the client computer are used to authenticate the client computer to access the server. A plurality of network addresses are received and used to identify the client computer in the network. In response to authenticating the client computer, the plurality of network addresses used to identify the client computer are forwarded to an access list for the server to allow the client computer to access the server. A message is sent to the client computer indicating access to the server allowed.
Current techniques for authenticating a client before the client can connect to a server have various flaws. Solutions that use an authentication mechanism to login at the server still expose the server to communications from malicious clients as part of the login process. Firewall techniques, such as captive portal, have constraints, including that the controls are implemented in the infrastructure and not in the server, which means the authentication infrastructure/firewall needs to be in a location where the server resides. In a multi-cloud world, fixed firewall infrastructure does not scale well and the firewall may not be portable if the infrastructure is moved, leaving the server exposed. Further, using firewall infrastructure for authentication relies on enterprise focused infrastructure teams to implement and the authentication is from a Lightweight Directory Access Protocol (LDAP) or enterprise directory, rather than a global identity provider (IDP).
Described embodiments provide improvements to authentication computer technology to address the above constraints of current firewall technology by having an authenticator, separate from the infrastructure controlling access, use information related to a DNS text record, which the client receives when requesting the DNS record when accessing the server, to authenticate the client and automatically update firewall access when the authentication succeeds.
In described embodiments, software on the client computer, such as a plug-in application or an installed application, retrieves the DNS record, including authentication parameters for authenticating through an authentication system. The client sends authentication parameters and a plurality of network addresses used by the client to the authenticator to authenticate the client. The authenticator upon authenticating the client, will update the firewall or proxy rules with all the network addressed provided by the client to allow client access to the server using any of the plurality of network addresses. The authenticator communicates with both the client and firewall and will make the necessary communications to complete the authentication and accept and send information needed to update the firewall.
Described embodiments add authentication capabilities to various network computing environments, including on-premises, cloud, hybrid cloud, and multi-cloud, to enable access to resources over different networks, with portability that follows resources from one cloud to another providing consistent access to resources from anywhere. Described embodiments provide security and identity and Secure Access Service Edge (SASE) capabilities by preventing access until an out-of-band authentication at the authenticator has occurred to protect the server resources from online security threats. Described embodiments render computing resources invisible and unavailable (e.g., ports, workloads, and applications) and only expose the resource after the user is authenticated and authorized.
The program components of
The network 116 may comprise a Storage Area Network (SAN), a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, and Intranet, peer-to-peer network, direct communication paths, etc.
The client authenticator 104 may validate (at block 308) the authenticator 106 using the out-of-band authentication parameters 208, 210, 212 from the DNS text record 200. If (at block 310) the authenticator 106 is not validated, then control ends with failing the client authentication. If (at block 310) the authenticator 106 is validated, then the client authenticator 104 sends (at block 312) a GET request to the ping address 212, e.g., a URL, indicated in field 212 of the DNS text record 200, to obtain a translated network address for the client computer 100, which may comprise the network address the client 100 would expect when connecting to the server 102. The network address from the ping address 212 may be different than the network address used to communicate with the server 102, such as a network address to route the client 100 communications to another location to exit the server 102 domain.
The client authenticator 104 sends (at block 314) an authentication request including client authentication information, e.g., client certificate, network addresses for the client, including the new address received from the GET request to the ping address 212, and out-of-band parameters indicated in the text record 200, to the authenticator domain name 206, e.g., “https://outofband.example.com/server.domain”.
In response to receiving (at block 320) the authentication request from the client authenticator program 104, the authenticator program 108 calls (at block 322) the authentication service 110 to authentication the client computer 100 using the client authentication information and other out-of-bound parameters in the DNS text record 200. If (at block 324) the authentication service 110 did not authenticate the client 100, then control ends with fail returned (at block 326) to the client computer 100. Otherwise, if (at block 324) the client is authenticated, then the authenticator program 108 captures (at block 326) the three network (IP) addresses for the client computer 100, including a client device assigned network address, IP address used to communicate with the server 102, and network address resulting from the GET request to the ping address 212. The captured client network addresses are sent (at block 330) to an allow list for the server 102 resource, which may be in a firewall, load balancer, proxy, etc. for the server 102. The authenticator program 108 sends (at block 332) a message to the client computer 100 indicating access to the server 102 is allowed. The client computer 100 may then use (at block 334) the server network address, e.g., 100.1.1.1, received with the text record to access the server 102.
With the embodiment of
In the embodiment of
In such case, the authenticator 106 may return the server 102 address, e.g., 10.1.1.1, at block 332 in
With the embodiment of
Further provided are a computer program product, system, and method for a client computer to authenticate with a server. The client computer receives a text record in response to a request for a domain name record for the server. The text record includes a domain name of an authenticator and authentication parameters to use to authenticate with the authenticator. The client computer submits the authentication parameters to the authenticator using the domain name of the authenticator. The authenticator uses the authentication parameters to authenticate the client computer to access the server. The client computer provides the authenticator a plurality of network addresses used to identify the client computer in a network. In response to the authenticator authenticating the client computer, the client computer receives a message from the authenticator that the client computer is authenticated to communicate to the server. The client computer uses a network address of the server to communicate with the server.
In a further client computer embodiment, the text record received in response to the request for a domain name record comprises a domain name service (DNS) text record received from a DNS server.
In a further client computer embodiment, the response to the request for the domain name record for the server includes the network address of the server.
In a further client computer embodiment, the response to the request for the domain name record for the server includes a network address of the authenticator, wherein the network address and the domain name of the authenticator are used to communicate with the authenticator.
In a further client computer embodiment, the client computer receives, from the authenticator, the network address of the server in response to the authenticator authenticating the client computer.
In a further client computer embodiment, the plurality of network addresses used to identify the client computer comprise a first network address assigned by the client computer, a second network address assigned by an Internet Service Provider for the client computer, and a third network address provided to optimize communications with the server.
In a further client computer embodiment, the client computer communicates with the server through a firewall that is provided the plurality of network addresses used to identify the client computer in the network.
In a further client computer embodiment, the authentication parameters indicate an authentication type. The client computer transmits to the authenticator a certificate for the client computer the authenticator uses to authenticate the client computer in response to the authentication parameters indicating the authentication type.
In a further client computer embodiment, the authentication parameters received from the authenticator indicate a ping address. The client computer further performs sending a request to the ping address and receiving a response to the request to the ping address comprising a translated network address for the client computer to use for the server, wherein one of the plurality of network addresses provided to the authenticator include the translated network address.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out aspects of the present invention.
Various aspects of the present disclosure are described by narrative text, flowcharts, block diagrams of computer systems and/or block diagrams of the machine logic included in computer program product (CPP) embodiments. With respect to any flowcharts, depending upon the technology involved, the operations can be performed in a different order than what is shown in a given flowchart. For example, again depending upon the technology involved, two operations shown in successive flowchart blocks may be performed in reverse order, as a single integrated step, concurrently, or in a manner at least partially overlapping in time.
A computer program product embodiment (“CPP embodiment” or “CPP”) is a term used in the present disclosure to describe any set of one, or more, storage media (also called “mediums”) collectively included in a set of one, or more, storage devices that collectively include machine readable code corresponding to instructions and/or data for performing computer operations specified in a given CPP claim. A “storage device” is any tangible device that can retain and store instructions for use by a computer processor. Without limitation, the computer-readable storage medium may be an electronic storage medium, a magnetic storage medium, an optical storage medium, an electromagnetic storage medium, a semiconductor storage medium, a mechanical storage medium, or any suitable combination of the foregoing. Some known types of storage devices that include these mediums include: diskette, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), static random access memory (SRAM), compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded device (such as punch cards or pits/lands formed in a major surface of a disc) or any suitable combination of the foregoing. A computer-readable storage medium, as that term is used in the present disclosure, is not to be construed as storage in the form of transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide, light pulses passing through a fiber optic cable, electrical signals communicated through a wire, and/or other transmission media. As will be understood by those of skill in the art, data is typically moved at some occasional points in time during normal operations of a storage device, such as during access, de-fragmentation or garbage collection, but this does not render the storage device as transitory because the data is not transitory while it is stored.
With respect to
COMPUTER 601 may take the form of a desktop computer, laptop computer, tablet computer, smart phone, smart watch or other wearable computer, mainframe computer, quantum computer or any other form of computer or mobile device now known or to be developed in the future that is capable of running a program, accessing a network or querying a database, such as remote database 630. As is well understood in the art of computer technology, and depending upon the technology, performance of a computer-implemented method may be distributed among multiple computers and/or between multiple locations. On the other hand, in this presentation of computing environment 600, detailed discussion is focused on a single computer, specifically computer 601, to keep the presentation as simple as possible. Computer 601 may be located in a cloud, even though it is not shown in a cloud in
PROCESSOR SET 610 includes one, or more, computer processors of any type now known or to be developed in the future. Processing circuitry 620 may be distributed over multiple packages, for example, multiple, coordinated integrated circuit chips. Processing circuitry 620 may implement multiple processor threads and/or multiple processor cores. Cache 621 is memory that is located in the processor chip package(s) and is typically used for data or code that should be available for rapid access by the threads or cores running on processor set 610. Cache memories are typically organized into multiple levels depending upon relative proximity to the processing circuitry. Alternatively, some, or all, of the cache for the processor set may be located “off chip.” In some computing environments, processor set 610 may be designed for working with qubits and performing quantum computing.
Computer-readable program instructions are typically loaded onto computer 601 to cause a series of operational steps to be performed by processor set 610 of computer 601 and thereby effect a computer-implemented method, such that the instructions thus executed will instantiate the methods specified in flowcharts and/or narrative descriptions of computer-implemented methods included in this document (collectively referred to as “the inventive methods”). These computer-readable program instructions are stored in various types of computer-readable storage media, such as cache 621 and the other storage media discussed below. The program instructions, and associated data, are accessed by processor set 610 to control and direct performance of the inventive methods. In computing environment 600, at least some of the instructions for performing the inventive methods may be stored in block 645 in persistent storage 613.
COMMUNICATION FABRIC 611 is the signal conduction path that allows the various components of computer 601 to communicate with each other. Typically, this fabric is made of switches and electrically conductive paths, such as the switches and electrically conductive paths that make up buses, bridges, physical input/output ports and the like. Other types of signal communication paths may be used, such as fiber optic communication paths and/or wireless communication paths.
VOLATILE MEMORY 612 is any type of volatile memory now known or to be developed in the future. Examples include dynamic type random access memory (RAM) or static type RAM. Typically, volatile memory 612 is characterized by random access, but this is not required unless affirmatively indicated. In computer 601, the volatile memory 612 is located in a single package and is internal to computer 601, but, alternatively or additionally, the volatile memory may be distributed over multiple packages and/or located externally with respect to computer 601.
PERSISTENT STORAGE 613 is any form of non-volatile storage for computers that is now known or to be developed in the future. The non-volatility of this storage means that the stored data is maintained regardless of whether power is being supplied to computer 601 and/or directly to persistent storage 613. Persistent storage 613 may be a read only memory (ROM), but typically at least a portion of the persistent storage allows writing of data, deletion of data and re-writing of data. Some familiar forms of persistent storage include magnetic disks and solid-state storage devices. Operating system 622 may take several forms, such as various known proprietary operating systems or open source Portable Operating System Interface-type operating systems that employ a kernel. The code included in block 645 typically includes at least some of the computer code involved in performing the inventive methods, including the authenticator program 108.
PERIPHERAL DEVICE SET 614 includes the set of peripheral devices of computer 601. Data communication connections between the peripheral devices and the other components of computer 601 may be implemented in various ways, such as Bluetooth connections, Near-Field Communication (NFC) connections, connections made by cables (such as universal serial bus (USB) type cables), insertion-type connections (for example, secure digital (SD) card), connections made through local area communication networks and even connections made through wide area networks such as the internet. In various embodiments, UI device set 623 may include components such as a display screen, speaker, microphone, wearable devices (such as goggles and smart watches), keyboard, mouse, printer, touchpad, game controllers, and haptic devices. Storage 624 is external storage, such as an external hard drive, or insertable storage, such as an SD card. Storage 624 may be persistent and/or volatile. In some embodiments, storage 624 may take the form of a quantum computing storage device for storing data in the form of qubits. In embodiments where computer 601 is required to have a large amount of storage (for example, where computer 601 locally stores and manages a large database) then this storage may be provided by peripheral storage devices designed for storing very large amounts of data, such as a storage area network (SAN) that is shared by multiple, geographically distributed computers. IoT sensor set 625 is made up of sensors that can be used in Internet of Things applications. For example, one sensor may be a thermometer and another sensor may be a motion detector.
NETWORK MODULE 615 is the collection of computer software, hardware, and firmware that allows computer 601 to communicate with other computers through WAN 602. Network module 615 may include hardware, such as modems or Wi-Fi signal transceivers, software for packetizing and/or de-packetizing data for communication network transmission, and/or web browser software for communicating data over the internet. In some embodiments, network control functions and network forwarding functions of network module 615 are performed on the same physical hardware device. In other embodiments (for example, embodiments that utilize software-defined networking (SDN)), the control functions and the forwarding functions of network module 615 are performed on physically separate devices, such that the control functions manage several different network hardware devices. Computer-readable program instructions for performing the inventive methods can typically be downloaded to computer 601 from an external computer or external storage device through a network adapter card or network interface included in network module 615.
WAN 602 is any wide area network (for example, the internet) capable of communicating computer data over non-local distances by any technology for communicating computer data, now known or to be developed in the future. In some embodiments, the WAN 602 may be replaced and/or supplemented by local area networks (LANs) designed to communicate data between devices located in a local area, such as a Wi-Fi network. The WAN and/or LANs typically include computer hardware such as copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and edge servers.
END USER DEVICE (EUD) 603 is any computer system that is used and controlled by an end user (for example, a customer of an enterprise that operates computer 601), and may take any of the forms discussed above in connection with computer 601. EUD 603 typically receives helpful and useful data from the operations of computer 601. For example, in a hypothetical case where computer 601 is designed to provide a recommendation to an end user, this recommendation would typically be communicated from network module 615 of computer 601 through WAN 602 to EUD 603. In this way, EUD 603 can display, or otherwise present, the recommendation to an end user. In some embodiments, EUD 603 may be a client device, such as thin client, heavy client, mainframe computer, desktop computer and so on. The EUD 603 may further comprise the client computer 100 including the client authenticator 104 as described with respect to
REMOTE SERVER 604 is any computer system that serves at least some data and/or functionality to computer 601. Remote server 604 may be controlled and used by the same entity that operates computer 601. Remote server 604 represents the machine(s) that collect and store helpful and useful data for use by other computers, such as computer 601. For example, in a hypothetical case where computer 601 is designed and programmed to provide a recommendation based on historical data, then this historical data may be provided to computer 601 from remote database 630 of remote server 604. The remote server 604 may comprise the authentication service 110 and server 102, as described with respect to
PUBLIC CLOUD 605 is any computer system available for use by multiple entities that provides on-demand availability of computer system resources and/or other computer capabilities, especially data storage (cloud storage) and computing power, without direct active management by the user. Cloud computing typically leverages sharing of resources to achieve coherence and economies of scale. The direct and active management of the computing resources of public cloud 605 is performed by the computer hardware and/or software of cloud orchestration module 641. The computing resources provided by public cloud 605 are typically implemented by virtual computing environments that run on various computers making up the computers of host physical machine set 642, which is the universe of physical computers in and/or available to public cloud 605. The virtual computing environments (VCEs) typically take the form of virtual machines from virtual machine set 643 and/or containers from container set 644. It is understood that these VCEs may be stored as images and may be transferred among and between the various physical machine hosts, either as images or after instantiation of the VCE. Cloud orchestration module 641 manages the transfer and storage of images, deploys new instantiations of VCEs and manages active instantiations of VCE deployments. Gateway 640 is the collection of computer software, hardware, and firmware that allows public cloud 605 to communicate through WAN 602. The public cloud 605 may further include the DNS server 112.
Some further explanation of virtualized computing environments (VCEs) will now be provided. VCEs can be stored as “images.” A new active instance of the VCE can be instantiated from the image. Two familiar types of VCEs are virtual machines and containers. A container is a VCE that uses operating-system-level virtualization. This refers to an operating system feature in which the kernel allows the existence of multiple isolated user-space instances, called containers. These isolated user-space instances typically behave as real computers from the point of view of programs running in them. A computer program running on an ordinary operating system can utilize all resources of that computer, such as connected devices, files and folders, network shares, CPU power, and quantifiable hardware capabilities. However, programs running inside a container can only use the contents of the container and devices assigned to the container, a feature which is known as containerization.
PRIVATE CLOUD 606 is similar to public cloud 605, except that the computing resources are only available for use by a single enterprise. While private cloud 606 is depicted as being in communication with WAN 602, in other embodiments a private cloud may be disconnected from the internet entirely and only accessible through a local/private network. A hybrid cloud is a composition of multiple clouds of different types (for example, private, community or public cloud types), often respectively implemented by different vendors. Each of the multiple clouds remains a separate and discrete entity, but the larger hybrid cloud architecture is bound together by standardized or proprietary technology that enables orchestration, management, and/or data/application portability between the multiple constituent clouds. In this embodiment, public cloud 605 and private cloud 606 are both part of a larger hybrid cloud.
CLOUD COMPUTING SERVICES AND/OR MICROSERVICES (not separately shown in
The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.
The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.
The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.
The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.
A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.
When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.
The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended.
