Secure credential management for client applications

By hashing the input credentials, distinguishing between fixed passwords and MFA credentials, the false affirmation problem is solved, and more accurate password storage and automatic completion are achieved, improving the user experience.

CN114245977BActive Publication Date: 2024-11-26INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080058114.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-09-09
Filing Date
2020-09-01
Publication Date
2024-11-26
Estimated Expiration
2040-09-01

AI Technical Summary

Technical Problem

The prior art can easily lead to false affirmation when distinguishing between fixed passwords and MFA credentials, resulting in user passwords not being stored, thereby affecting user experience.

Method used

By hashing the entered credentials, we can determine whether to use MFA. If it matches, the credentials will be stored to achieve automatic completion.

Benefits of technology

Improves the accuracy of password storage, avoids false affirmation, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114245977B_ABST
    Figure CN114245977B_ABST
Patent Text Reader

Abstract

A method and system for managing security credentials for a client application is provided. The method includes: detecting that a user is entering security credentials for authenticating a client application; hashing at least a portion of the entered credentials to obtain a current hashed credential and storing the current hashed credential; and comparing the current hashed credential with a previously stored hashed credential for the client application. If the current hashed credential matches the previously stored hashed credential, the method may store the credential for automatic completion of the credential for the client application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to secure credential management, and in particular, to secure credential management for storing reusable credentials for client applications. Background Art

[0002] The client application may be configured to store a user login identification and password. Some client computing devices may use a password management service to store their user's login credentials for different client applications.

[0003] The stored credentials can be automatically transmitted to the network server to initiate user authorization. This process increases user convenience by eliminating the time required to re-enter credentials from a known client computer.

[0004] To enhance network security measures, many companies have adopted multi-factor authentication (MFA) protocols, in which users enter two forms of identification in order to access an application or network. In many MFA systems, the first form of identification is a fixed password, and the second form of identification is a one-time password (OTP) generated for a specific instance and expires after use or a period of time.

[0005] MFA provides secure authentication by requiring credentials from different sources. In other words, the source of the first credential should be different from the source of the second credential.

[0006] The user may enter a primary identification, and the second credential may be a one-time password (OTP) generated by a security token. The OTP may be any combination of numbers, letters, and symbols in the form of a password or PIN. The OTP may be generated by a device owned by the user, such as a key ring device or smart card with an OTP generator, or by a software token embedded in a smartphone, tablet, personal computer, or another computing device, or may be received via a cell phone or email message. Once entered, the first credential and the second credential are transmitted to an authentication mechanism to verify the credentials and grant or restrict the user's access to an application, network, or server.

[0007] The security credentials may be a cascade of a fixed password and an OTP. In these cases, the software application should only store the first form of identification, because retransmitting a set of expired credentials will only result in the authentication mechanism denying access to the user.

[0008] Methods are known for analyzing input security credentials to determine if they are MFA credentials to find out if they should be stored for automatic entry. One known method evaluates the rhythm of the keystrokes of the security credentials to identify pauses between the entry of a fixed password and the entry of an OTP. If it is determined that MFA is not being used, the client will store the password and reuse it when the session expires. However, if it is determined that MFA is being used, the client will not store the password and will re-prompt the user for it each time to avoid invalidating the user's password.

[0009] Therefore, there is a need in the art to solve the above problems. Summary of the invention

[0010] From a first aspect, the present invention provides a computer-implemented method for security credential management for a client application, comprising: detecting that a user is entering security credentials for authenticating a client application; hashing at least a portion of the input credentials to obtain a current hash credential and storing the current hash credential; comparing the current hash credential with a previously stored hash credential of the client application; and if the current hash credential matches the previously stored hash credential, storing the detected security credential for automatically completing the security credential required for the client application.

[0011] From another aspect, the present invention provides a computer system for managing security credentials for client applications, comprising: a processor and a memory, the memory being configured to provide computer program instructions to the processor to perform the functions of the following components: a credential detection component for detecting that a user is entering security credentials for authenticating a client application; a hashing component for hashing at least a portion of the input credentials to obtain a current hash credential, and a hash storage component for storing the current hash credential; a comparison component for comparing the current hash credential with a previously stored hash credential of the client application; and an automatic credential component for storing the detected security credential for automatically completing the credential storage component for the security credential for the client application if the current hash credential matches the previously stored hash credential.

[0012] From another aspect, the present invention provides a computer program product for security credential management for a client application, the computer program product comprising a computer-readable storage medium having program instructions embodied therein, the program instructions being executable by a processor to cause the processor to: detect that a user is entering security credentials for authenticating a client application; hash at least a portion of the input credentials to obtain a current hash credential and store the current hash credential; compare the current hash credential with a previously stored hash credential of the client application; and if the current hash credential matches the previously stored hash credential, store the detected security credential for automatically completing the security credential of the client application.

[0013] Viewed from another aspect, the present invention provides a computer program product for secure credential management for client applications, the computer program product comprising a computer-readable storage medium readable by a processing circuit and storing instructions executable by the processing circuit to perform a method for performing the steps of the present invention.

[0014] Viewed from another aspect, the invention provides a computer program stored on a computer readable medium and loadable into the internal memory of a digital computer, comprising software code portions for performing the steps of the invention when said program is run on a computer.

[0015] According to one aspect of the present invention, a computer-implemented method for security credential management for a client application is provided, comprising: detecting that a user is entering security credentials for authenticating a client application; hashing at least a portion of the entered credentials to obtain a current hash credential and storing the current hash credential; comparing the current hash credential with a previously stored hash credential of the client application; and if the current hash credential and the previously stored hash credential match, storing the credential for use in automatically completing the credentials of the client application.

[0016] According to another aspect of the present invention, a system for security credential management for client applications is provided, comprising: a processor and a memory, the memory being configured to provide computer program instructions to the processor to perform the functions of the following components: a credential detection component for detecting that a user is entering security credentials for authenticating a client application; a hashing component for hashing at least a portion of the input credentials to obtain a current hash credential, and a hash storage component for storing the current hash credential; a comparison component for comparing the current hash credential with a previously stored hash credential of the client application; and an automatic credential component for storing the credential for automatically completing the credential for the client application if the current hash credential matches the previously stored hash credential.

[0017] According to another aspect of the present invention, a computer program product for security credential management for a client application is provided, the computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions being executable by a processor to cause the processor to: detect that a user is entering security credentials for authenticating a client application; hash at least a portion of the input credentials to obtain a current hash credential and store the current hash credential; compare the current hash credential with a previously stored hash credential of the client application; and if the current hash credential matches the previously stored hash credential, store the credential for use in automatically completing the credentials of the client application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The subject matter of the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification.The invention, both as to its organization and method of operation, together with objects, features, and advantages thereof, may be best understood by reference to the following detailed description when read in connection with the accompanying drawings.

[0019] Preferred embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which:

[0020] Figure 1 is a block diagram of an example embodiment of a system in which the present invention may be implemented;

[0021] Figure 2 is a flow chart of a first exemplary embodiment of a method according to the present invention;

[0022] Figure 3 is a flow chart of a second exemplary embodiment of a method according to the present invention;

[0023] Figure 4 is a block diagram of an example embodiment of a system according to the present invention;

[0024] Figure 5 is a block diagram of an embodiment of a computer system or cloud server in which the present invention may be implemented;

[0025] Figure 6 is a schematic diagram of a cloud computing environment in which the present invention may be implemented; and

[0026] Figure 7 is a diagram of an abstract model layer of a cloud computing environment in which the present invention may be implemented.

[0027] It should be understood that for simplicity and clarity of illustration, the elements shown in the figures are not necessarily drawn to scale. For example, for clarity, the dimensions of some elements may be enlarged relative to other elements. In addition, where deemed appropriate, reference numerals may be repeated in the drawings to indicate corresponding or similar features. DETAILED DESCRIPTION

[0028] A method and system for secure credential management for client applications is described. The secure credential management stores credentials that are automatically provided when using a client application. However, the management needs to distinguish between fixed secure credentials and secure credentials that change due to MFA methods. In particular, MFA methods can cascade an OTP with a fixed password to form a credential.

[0029] Embodiments of the present invention recognize that current MFA analysis and methods may result in false positives when identifying MFA credentials. False positives will result in the user's password not being stored, resulting in a poor user experience. False positives may occur when a user enters a complex password that ends with a date or number combination that they must remember, and therefore will result in the second half of the password having a slower keystroke input speed.

[0030] Embodiments of the present invention provide a solution for comparing currently provided credentials with previously entered credentials for a client application by comparing hashes of the entire credential or one or more portions of the credential.

[0031] In one embodiment, the entire credential is compared, and if they match, the credential is suitable for being stored for use in the auto-completion client application. This can be used as a backup check when an analysis has been performed that suggests the credential is an MFA credential that should not be stored.

[0032] In another embodiment, the credential may be split into two parts, the first part being assumed to be a fixed password and the second part being assumed to be a mutable token such as an OTP. At least the second part may be hashed and compared to a previously hashed version of the second part to see if that part is in fact a mutable token. In another variation, the two parts are compared as further explained below.

[0033] The method detects the use of MFA by a user on the client side using a piece of client software that runs a simple heuristic to check whether the entered credentials include an MFA token by comparing the password and token each time they are entered.

[0034] refer to Figure 1 , provides an exemplary embodiment of a system 100 in which the present invention may be implemented. The system 100 may include a client computing device 130 having a client application 134 that requires authentication when connecting to an associated remote server 110 or network.

[0035] The client computing device 130 may include at least one processor 131, a hardware module or circuit for performing the functions of the described components, which may be a software unit executed on at least one processor. Multiple processors running parallel processing threads may be provided to enable parallel processing of some or all functions of the components. The memory 132 may be configured to provide computer instructions 133 to the at least one processor 131.

[0036] Computer instructions 133 may include a client application 134 that requires authentication, such as through an authentication component 135 of the application. Client computing device 130 may also include an input / output device 136 for inputting credentials into authentication component 135, which may be a keyboard, mouse, touch screen display, etc.

[0037] Authentication component 135 may use MFA where an OTP is provided from another source, such as OTP providing device 120, for input to client application 134 authentication component 135 via I / O device 136. The OTP may be input cascaded to a fixed password of a user of client application 134.

[0038] The described system provides a credential security management component 160 for managing credential entry via a client computing device 130. The credential security management component 160 may be provided locally to the client computing device 130 or may be provided as a secure remote service. The credential security management component 160 may provide a credential storage component 163 for storing credentials at the client computing device 130 or remotely at a storage device 170 via a secure communication channel, and an auto-completion component 164 for automatically completing credentials in the authentication component 135.

[0039] The credential security management component 160 may include an MFA identification component 161 for identifying when the authentication component 135 is using MFA in order to evaluate which credentials can be stored for auto-completion. The described system provides a credential checking component 162 for verifying whether the credential is a mutable MFA credential that should not be stored or a fixed credential that can be stored.

[0040] refer to Figure 2 , flowchart 200 illustrates a first example embodiment of the described method performed by credential security management component 160 .

[0041] The method may receive 201 input of user credentials for a client application. It may be determined 202 whether the credentials include possible use of MFA. This may be determined by various methods, including analyzing the rhythm of input keystrokes of the credentials to determine if there is a delay or slower input of a portion of the credentials that indicates use of a mutable token such as an OTP. In one embodiment, the possible use of MFA is measured by a threshold probability.

[0042] If it is determined that the credentials are not possible using MFA, the credentials may be stored 207 for future auto-completion.

[0043] However, if it is determined that the credential may use MFA, this can be checked by securely hashing 203 the entire string of the input credential and storing the result. A secure hash may apply a one-way cryptographic hash function to produce a message digest of the credential. The message digest may be securely stored and may be used to verify that another message digest has been generated from the same input credential. Verification is performed by comparing 204 the currently generated message digest with a stored previously generated message digest of a previously input credential.

[0044] It may be determined 205 whether the message digests match. If so, this indicates that the credential does not include a mutable token and may be stored 207 for use in automatically completing authentication.

[0045] If it is determined 205 that the message digests do not match, this indicates that the credentials either include a mutable token as used in MFA, or that the credentials have changed, so the credentials are not stored 206. If the credentials have changed due to a password update, and do not include a mutable token, the message digest generated the next time the credentials are entered will match the generated message digest, and the credentials will be stored.

[0046] The message may then await input of the next credential 210 and the method may repeat.

[0047] refer to Figure 3 , flowchart 300 illustrates a second example embodiment of the described method performed by the credential security management component 160 .

[0048] In a manner similar to the first embodiment, the method may receive 301 input of user credentials for a client application. It may be determined 302 whether the credentials include possible use of MFA. This may be determined by various methods, including analyzing the rhythm of input keystrokes of the credentials to determine if there is a delay or slower input of a portion of the credentials that indicates use of a mutable token such as an OTP. In one embodiment, the possible use of MFA is measured by a threshold probability.

[0049] If it is determined 303 that the credentials are not possible using MFA, then the credentials may be stored 321 for future auto-completion.

[0050] However, if it is determined 303 that the credential may use MFA, the method may divide 304 the credential based on an analysis of whether MFA is being used, and may analyze 305 the divided portions to determine a presumed fixed password portion and a presumed variable token portion. For example, a method using an input key stroke rhythm may indicate a clear distinction between two portions of the credential, one portion of which may be presumed to be a fixed password and one portion of which may be presumed to be a variable token such as an OTP.

[0051] For example, if the rhythm of the keystrokes indicates a pause during input, the pause can show the division between the two parts, and the comparative speed of input of the keystrokes in each part can indicate a known fixed password by faster input than a newly received variable token. Another way to determine if a part is a variable token is to analyze the characters, and a part that is primarily numeric can indicate a variable token.

[0052] The method may take 306 a secure hash of the assumed fixed password portion and may store the resulting message digest. The currently generated message digest may be compared 307 to a previously stored message digest.

[0053] The method may also securely hash the assumed mutable token portion 308 and may store the resulting message digest. The currently generated message digest may be compared 309 with a previously stored message digest.

[0054] Hash comparisons can use a non-salted hashing algorithm such as MD5, SHA, or SHA256. This means that the hash of a particular string will always be the same and can therefore be compared directly. It is not possible to use these non-cryptographic hashing algorithms when sending passwords over the wire, as they are not as secure as newer encryption algorithms; however, they are secure enough to be stored locally by the client for the purpose of determining whether MFA is being used.

[0055] It may be determined 310 whether the message digest of the assumed variable token portion matches. If so, this indicates that the assumed variable token portion is actually fixed and MFA is not being used, so the credential may be stored 321 for future auto-completion. This may occur, for example, when the assumed variable token is actually a date at the end of a password or other password portion that may have a slower input cadence.

[0056] If it is determined 310 that the message digests of the assumed variable token portions do not match, then they are actually variables indicating that MFA is being used in the credential. The method may then determine 311 whether the message digests of the assumed fixed password portions match. If so, it may be assumed 322 that the credential is using MFA and that at least the token portion should not be stored. The fixed password portion may be stored for future auto-completion.

[0057] If determined 311 , if the message digest of the assumed fixed password portion does not match, this may indicate that the password has been reset 323 and the credentials should not be stored until the next iteration in which a new password is confirmed.

[0058] In all cases, the method may then wait 324 for the next input of credentials for verification. The correctness of the assumption that MFA is being used may be verified over multiple authentication attempts or at each authentication.

[0059] The method uses software on the client side to detect the split between a fixed password and a mutable token and hash both parties, store them, and compare the two each time credentials are needed by checking that the password portion remains the same and the token portion changes each time.

[0060] Known methods can be used to detect whether a credential is likely to be using MFA. If MFA is likely to be in use, an additional step is performed to verify whether the credential includes a variable portion, rather than not storing the password at this time. The user's password may end up at a date that can be interpreted as a token by the MFA analysis system, and a false positive for MFA can be assumed when in fact the credential is fixed and can be stored.

[0061] In situations where the server does not already know whether MFA is being used, this method can be used to provide a deeper analysis of the differences between the two entered credentials to determine if an MFA token is being used.

[0062] refer to Figure 4 , the block diagram shows Figure 1 Further details of the credential checking component 162 of the credential security management component 160 are provided.

[0063] Credential checking component 162 may include credential detection component 401 for detecting that a user is entering security credentials for authenticating a client application. Credential detection component 401 may be limited to credentials determined by MFA recognition component 161 to have a threshold probability of using an MFA method.

[0064] The credential checking component 162 may include a credential splitting component 402 for splitting the input security credential into a first portion and a second portion based on an analysis of the input security credential to identify a pause or change in rhythm of the input between the first portion and the second portion. The credential checking component 162 may include a portion identification component 403 for determining, by analyzing the input of the credential, that the first portion or the second portion is a hypothetical variable token portion, and the other of the first portion or the second portion is a hypothetical fixed password portion.

[0065] The credential checking component 162 may include a hashing component 404 for hashing at least a portion of the input credentials to obtain a current hashed credential, a hash storage component 406 for storing the current hashed credential, and a comparison component 405 for comparing the current hashed credential with a previously stored hashed credential of the client application.

[0066] The hashing component 404 and the comparing component 405 may operate on the entire credential string or on one or both of the first portion and the second portion, respectively.

[0067] The credential security management component 160 may include an automatic credential component 164 and a credential storage component 163 for storing credentials for automatic completion of credentials for client applications if MFA is not used in the authentication credentials.

[0068] In an embodiment where the credential is divided into a hypothetical fixed password portion and a hypothetical variable token portion, the following may occur.

[0069] If the comparison component 405 determines that the current hashed credential of the assumed mutable token portion matches a previously stored hashed credential, the credential storage component 163 can store the credential for the auto-completion client application.

[0070] If the comparison component 405 determines that the current hash credential of the assumed variable token portion does not match the previously stored hash credential, and the current hash credential of the assumed fixed password portion matches the previously stored hash credential, the credential storage component 163 can store the assumed fixed password portion for use in automatically completing the partial credentials of the client application.

[0071] If the comparison component 405 determines that the current hashed credential of the assumed fixed password portion does not match a previously stored hashed credential, the credential storage component 164 can wait for the next input credential before storing the credential for use in automatically completing the client application's credentials.

[0072] Figure 5 Describes an embodiment of the present invention Figure 1 1 is a block diagram of the components of the client computing device 130 of the system 100. It should be understood that Figure 5 This merely provides an illustration of one implementation and does not imply any limitation with respect to the environments in which different embodiments may be implemented.Many modifications to the described environments may be made.

[0073] The client computing device 130 may include one or more processors 502, one or more computer-readable RAMs 504, one or more computer-readable ROMs 506, one or more computer-readable storage media 508, device drivers 512, read / write drivers or interfaces 514, and network adapters or interfaces 516, all interconnected by a communications fabric 518. Communications fabric 518 may be implemented with any architecture designed to pass data and / or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within the system.

[0074] One or more operating systems 510 and application programs 511 such as client applications 131 and credential security management components are stored on one or more computer-readable storage media 508 for execution by one or more processors 502 via one or more corresponding RAMs 504 (typically including cache memories). In the illustrated embodiment, each computer-readable storage medium 508 may be a disk storage device of an internal hard drive, a CD-ROM, a DVD, a memory stick, a tape, a disk, an optical disk, a semiconductor storage device such as RAM, ROM, EPROM, flash memory, or any other computer-readable storage medium that can store computer programs and digital information, in accordance with embodiments of the present invention.

[0075] The client computing device 130 may also include a R / W drive or interface 514 to read from and write to one or more portable computer-readable storage media 526. Applications 511 on the client computing device 130 may be stored on one or more of the portable computer-readable storage media 526, read via a corresponding R / W drive or interface 514, and loaded into a corresponding computer-readable storage medium 508.

[0076] The client computing device 130 may also include a network adapter or interface 516, such as a TCP / IP adapter card or a wireless communication adapter. Application programs 511 on the client computing device 130 may be downloaded to the computing device from an external computer or external storage device via a network (e.g., the Internet, a local area network or other wide area network or wireless network) and the network adapter or interface 516. The program may be loaded from the network adapter or interface 516 into the computer-readable storage medium 508. The network may include copper wires, optical fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and edge servers.

[0077] The client computing device 130 may also include a display screen 520, a keyboard or keypad 522, and a computer mouse or touchpad 524. The device driver 512 interfaces with the display screen 520 for imaging, the keyboard or keypad 522, the computer mouse or touchpad 524, and / or the display screen 520 for pressure sensing of alphanumeric character input and user selection. The device driver 512, the R / W driver or interface 514, and the network adapter or interface 516 may include hardware and software stored in the computer-readable storage medium 508 and / or the ROM 506.

[0078] The present invention may be a system, method and / or computer program product at any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or multiple media) having computer-readable program instructions thereon, and the computer-readable program instructions are used to cause a processor to perform various aspects of the present invention.

[0079] Computer readable storage medium can be a tangible device capable of retaining and storing instructions used by an instruction execution device. Computer readable storage medium can be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer readable storage medium includes the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device such as a punch card or a raised structure in a groove with instructions recorded thereon, and any suitable combination of the foregoing. As used herein, computer readable storage medium should not be interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (e.g., a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.

[0080] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.

[0081] The computer-readable program instructions for performing the operation of the present invention may be assembly instructions, instruction set architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, configuration data of an integrated circuit, or source code or object code written in any combination of one or more programming languages ​​(including object-oriented programming languages, such as Smalltalk, C++, etc.) and process programming languages ​​(such as "C" programming language or similar programming languages). The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider via the Internet). In some embodiments, in order to perform various aspects of the present invention, an electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute a computer-readable program instruction by utilizing the state information of the computer-readable program instructions to personalize the electronic circuit.

[0082] Various aspects of the present invention are described herein with reference to the flow chart and / or block diagram of the method, device (system) and computer program product according to embodiments of the present invention. It will be understood that each frame of the flow chart and / or block diagram and the combination of frames in the flow chart and / or block diagram can be implemented by computer-readable program instructions.

[0083] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing apparatus create a device for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0084] These computer-readable program instructions may also be stored in a computer-readable storage medium, which may direct a computer, a programmable data processing apparatus and / or other device to work in a specific manner, so that the computer-readable storage medium in which the instructions are stored includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0085] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0086] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention.In this regard, each frame in the flow chart or block diagram can represent a module, segment or part of an instruction, which includes one or more executable instructions for realizing the specified logical function.In some alternative implementations, the function noted in the frame may not occur in the order noted in the figure.For example, the two frames shown in succession can actually be performed substantially simultaneously, or these frames can sometimes be performed in reverse order, depending on the function involved.It will also be noted that each frame of the block diagram and / or flow chart illustration and the combination of the frames in the block diagram and / or flow chart illustration can be realized by a dedicated hardware-based system that performs a specified function or action or performs a combination of special hardware and computer instructions.

[0087] cloud computing

[0088] It should be understood that although the present disclosure includes detailed descriptions about cloud computing, the implementation of the teachings set forth herein is not limited to cloud computing environments. Instead, embodiments of the present invention can be implemented in conjunction with any other type of computing environment now known or later developed.

[0089] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be quickly provisioned and released with minimal management effort or interaction with the provider of the service. The cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

[0090] Features are as follows:

[0091] On-demand self-service: Cloud consumers can unilaterally and automatically provision computing capabilities, such as server time and network storage, as needed, without requiring manual interaction with the provider of the service. Wide area network access: Capabilities are available over the network and accessed through standard mechanisms that facilitate use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

[0092] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, where different physical and virtual resources are dynamically allocated and reallocated based on demand. There is location independence in the sense that consumers typically do not control or know the exact location of the resources provided, but are able to specify the location at a higher level of abstraction (e.g., country, state, or data center).

[0093] Rapid elasticity: In some cases, the ability to scale out quickly and in quickly can be provisioned quickly and elastically. To the consumer, the capacity available for provisioning often appears to be unlimited and can be purchased in any quantity at any time.

[0094] Metered Services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both providers and consumers of the utilized services.

[0095] The service model is as follows:

[0096] Software as a Service (SaaS): The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from a variety of client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including the network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

[0097] Platform as a Service (PaaS): The capability provided to consumers is to deploy consumer-created or acquired applications onto cloud infrastructure, where the applications are created using programming languages ​​and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possible configuration of the application hosting environment.

[0098] Infrastructure as a Service (IaaS): The capabilities provided to consumers are processing, storage, networking, and other basic computing resources on which consumers can deploy and run arbitrary software, which may include operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but have control over the operating system, storage, deployed applications, and possibly limited control over selected networking components (e.g., host firewalls).

[0099] The deployment model is as follows:

[0100] Private Cloud: The cloud infrastructure is operated only for the organization. It can be managed by the organization or a third party and can exist inside or outside the building.

[0101] Community cloud: The cloud infrastructure is shared by several organizations and supports a specific community with shared concerns (e.g., mission, security requirements, policies, and compliance considerations). It can be managed by the organization or a third party and can exist on-premises or off-premises.

[0102] Public cloud: Cloud infrastructure is available to the general public or large industrial groups and is owned by an organization that sells cloud services.

[0103] Hybrid cloud: A cloud infrastructure is a combination of two or more clouds (private, community or public) that remain a unique entity but are bound together by standardized or proprietary technologies that enable data and application portability (e.g., cloud bursting for load balancing between clouds).

[0104] The cloud computing environment is service-oriented, with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure consisting of a network of interconnected nodes.

[0105] Reference now Figure 6 , depicts an illustrative cloud computing environment 50. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10 with which a local computing device used by a cloud consumer can communicate, such as a personal digital assistant (PDA) or cellular phone 54A, a desktop computer 54B, a laptop computer 54C, and / or an automobile computer system 54N. The nodes 10 can communicate with each other. They can be physically or virtually grouped (not shown) in one or more networks, such as a private cloud, community cloud, public cloud, or hybrid cloud, or a combination thereof, as described above. This allows the cloud computing environment 50 to provide infrastructure, platform, and / or software as a service for which the cloud consumer does not need to maintain resources on a local computing device. It should be understood that Figure 6 The types of computing devices 54A-N shown in are intended for illustration only, and computing node 10 and cloud computing environment 50 may communicate with any type of computing device over any type of network and / or network addressable connection (eg, using a web browser).

[0106] Reference now Figure 7 , showing the cloud computing environment 50 ( Figure 6 ) provides a set of functional abstraction layers. It should be understood in advance that Figure 7 The components, layers, and functions shown in are intended to be illustrative only, and embodiments of the present invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

[0107] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include: host 61; server 62 based on RISC (Reduced Instruction Set Computer) architecture; server 63; blade server 64; storage device 65; and network and network components 66. In some embodiments, software components include network application server software 67 and database software 68.

[0108] Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual servers 71 ; virtual storage 72 ; virtual networks 73 , including virtual private networks; virtual applications and operating systems 74 ; and virtual clients 75 .

[0109] In one example, the management layer 80 may provide the functionality described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources for performing tasks within a cloud computing environment. Metering and pricing 82 provides cost tracking when resources are utilized in a cloud computing environment, as well as bills or invoices for consuming these resources. In one example, these resources may include application software licenses. Security provides authentication for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management so that the required service levels are met. Service level agreement (SLA) planning and fulfillment 85 provides pre-scheduling and procurement of cloud computing resources, where future demand is anticipated based on the SLA.

[0110] The workload layer 90 provides examples of functions that can take advantage of the cloud computing environment. Examples of workloads and functions that can be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analysis processing 94; transaction processing 95; and security credential management processing 96.

[0111] The description of various embodiments of the present invention has been given for the purpose of illustration, but it is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or technical improvements existing in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

[0112] Improvements and modifications may be made to the foregoing without departing from the scope of the present invention.

Claims

1. A computer-implemented method for secure credential management for a client application, comprising: Detect that the user is entering security credentials for authenticating the client application; hashing at least a portion of the input credential to obtain a current hashed credential and storing the current hashed credential; comparing the current hashed credential to a previously stored hashed credential for the client application; as well as If the current hashed credential matches the previously stored hashed credential, storing the detected security credential for use in automatically completing the security credential required for the client application; A threshold probability that a user is utilizing a multi-factor authentication method is determined based on a cadence of entering security credentials.

2. The computer-implemented method of claim 1 , further comprising: Based on an analysis of input security credentials, the input security credentials are split into a first part and a second part to identify a pause or change in the rhythm of the input between the first part and the second part, wherein hashing and comparing the input credentials are performed for one or both of the first part and the second part, respectively.

3. The computer-implemented method of claim 2, further comprising: It is determined by analyzing the input of the credential that the first portion or the second portion is a hypothetical variable token portion and the other of the first portion or the second portion is a hypothetical fixed password portion.

4. The computer-implemented method of claim 3, wherein if the current hash credential of the assumed mutable token portion matches the previously stored hash credential, storing the security credential for use in automatically completing the security credential of the client application.

5. A computer-implemented method according to claim 3, wherein if the current hash credential of the assumed variable token portion does not match the previously stored hash credential, and the current hash credential of the assumed fixed password portion and the previously stored hash credential match, storing the assumed fixed password portion for automatically completing the partial credentials of the client application.

6. The computer-implemented method of claim 3, wherein if the current hashed credential of the assumed fixed password portion does not match the previously stored hashed credential, the method is repeated for a subsequent input credential before storing the credential for use in automatically completing the credential for the client application.

7. The computer-implemented method of claim 1, wherein the method is performed at a client computing device for storing credentials at the client computing device for use in automatically completing the credentials for a client application.

8. The computer-implemented method of any one of claims 1 to 7, wherein the method is performed for a client computing device at a remote service for storing credentials at the client computing device for use in automatically completing the credentials for a client application.

9. A computer system for secure credential management for a client application, comprising: A processor and a memory, the memory being configured to provide computer program instructions to the processor to perform the functions of: A credential detection component, used to detect that a user is entering security credentials for authenticating a client application; a hashing component for hashing at least a portion of the input credential to obtain a current hashed credential, and a hash storage component for storing the current hashed credential; a comparison component for comparing the current hashed credential with a previously stored hashed credential for the client application; and an automatic credential component for storing the detected security credential for automatic completion of the security credential for the client application if the current hash credential matches the previously stored hash credential; A multi-factor authentication identification component is used to determine a threshold probability that a user is using a multi-factor authentication method based on a cadence of entering security credentials.

10. The computer system of claim 9, further comprising: a credential splitting component for splitting the inputted security credential into a first portion and a second portion based on an analysis of the inputted security credential to identify a pause or change in a tempo of the input between the first portion and the second portion; The hashing component and the comparing component operate on one or both of the first portion and the second portion, respectively.

11. The computer system of claim 10, further comprising: a portion identification component for determining the first portion or the second portion by analyzing the input of the credential; The part is a hypothetical variable token part and the other of the first part or the second part is a hypothetical fixed password part.

12. The computer system according to claim 11, wherein: If the comparison component determines that the current hashed credential of the hypothetical mutable token portion matches the previously stored hashed credential, the credential storage component stores the credential for use in automatically completing the credential for the client application.

13. The computer system according to claim 11, wherein: If the comparison component determines that the current hash credential of the assumed variable token portion does not match the previously stored hash credential, and the current hash credential of the assumed fixed password portion matches the previously stored hash credential, the credential storage component stores the assumed fixed password portion for use in automatically completing a portion of the credentials of the client application.

14. The computer system according to claim 11, wherein: If the comparison component determines that the current hashed credential of the assumed fixed password portion does not match the previously stored hashed credential, the credential storage component awaits a subsequently entered credential before storing the credential for use in automatically completing the credential for the client application.

15. The computer system of claim 9, wherein the system is executed at a client computing device for storing credentials at the client computing device for use in automatically completing the credentials for client applications.

16. The computer system of any one of claims 9 to 15, wherein the system is executed for a client computing device at a remote service for storing credentials at the client computing device for automatically completing the credentials for a client application.

17. A computer program product for secure credential management for a client application, the computer program product comprising: A computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit, the instructions for performing the method according to any one of claims 1 to 8.

18. A computer-readable storage medium comprising a computer program stored on the computer-readable medium and loadable into the internal memory of a digital computer, the computer program comprising software code portions for executing the method according to any one of claims 1 to 8 when the program is run on a computer.