Preventing unauthorized access to secured information systems using tokenized authentication techniques

A computing platform may receive, from a social messaging server, a request to authenticate a user to a user account associated with a client portal. In response to receiving the request, the computing platform may send, to the social messaging server, an authentication token request message. Thereafter, the computing platform may receive, from the social messaging server, an authentication token. The computing platform may validate the authentication token received from the social messaging server. Based on validating the authentication token received from the social messaging server, the computing platform may generate a validation message directing a client support server to provide the user with access to the user account. Subsequently, the computing platform may send the validation message to the client support server, which may cause the client support server to initiate a client support session with the user via the social messaging service provided by the social messaging server.

BACKGROUND

Aspects of the disclosure relate to providing information security and preventing unauthorized access to resources of an information system. In particular, one or more aspects of the disclosure relate to preventing unauthorized access to secured information systems using tokenized authentication techniques.

As organizations increasingly provide electronic portals via which various users may access, view, and/or modify information, including client information, ensuring the safety and security of information maintained by such organizations and/or made available via such portals is increasingly important. In many instances, however, it may be difficult to ensure the safety and security of such information while also optimizing the efficient and effective technical operations of the computer systems that maintain such information and/or provide such portals.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, and convenient technical solutions that address and overcome the technical problems associated with providing information security and preventing unauthorized access to resources of an information system by implementing tokenized authentication techniques.

In accordance with one or more embodiments, a computing platform having at least one processor, a memory, and a communication interface may receive, via the communication interface, and from a social messaging server, a request to authenticate a first user to a first user account associated with a client portal provided by a client portal server. Based on receiving the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server, the computing platform may send, via the communication interface, and to the social messaging server, a first authentication token request message. Thereafter, the computing platform may receive, via the communication interface, and from the social messaging server, a first authentication token. Subsequently, the computing platform may validate the first authentication token received from the social messaging server. Based on validating the first authentication token received from the social messaging server, the computing platform may generate a first validation message directing a client support server to provide the first user with access to the first user account. Subsequently, the computing platform may send, via the communication interface, and to the client support server, the first validation message directing the client support server to provide the first user with access to the first user account.

In some embodiments, the first authentication token received from the social messaging server may include information indicating that the first user is authenticated to a first social messaging service account associated with a social messaging service provided by the social messaging server.

In some embodiments, the social messaging server may generate the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server based on receiving chat input from a first client computing device associated with the first user.

In some embodiments, the first validation message directing the client support server to provide the first user with access to the first user account may include information indicating that the first user has been authenticated to the first user account based on the first authentication token received from the social messaging server.

In some embodiments, the first validation message directing the client support server to provide the first user with access to the first user account may include information directing the client support server to initiate a first client support session with the first user via the social messaging service provided by the social messaging server.

In some embodiments, the computing platform may receive, via the communication interface, and from the social messaging server, a request to authenticate a second user to a second user account associated with the client portal provided by the client portal server. Based on receiving the request to authenticate the second user to the second user account associated with the client portal provided by the client portal server, the computing platform may send, via the communication interface, and to the social messaging server, a second authentication token request message. Thereafter, the computing platform may receive, via the communication interface, and from the social messaging server, a second authentication token. Subsequently, the computing platform may validate the second authentication token received from the social messaging server. Based on validating the second authentication token received from the social messaging server, the computing platform may generate a second validation message directing the client support server to provide the second user with access to the second user account. Subsequently, the computing platform may send, via the communication interface, and to the client support server, the second validation message directing the client support server to provide the second user with access to the second user account.

In some embodiments, the second authentication token received from the social messaging server may include information indicating that the second user is authenticated to a second social messaging service account associated with the social messaging service provided by the social messaging server.

In some embodiments, the social messaging server may generate the request to authenticate the second user to the second user account associated with the client portal provided by the client portal server based on receiving chat input from a second client computing device associated with the second user.

In some embodiments, the second validation message directing the client support server to provide the second user with access to the second user account may include information indicating that the second user has been authenticated to the second user account based on the second authentication token received from the social messaging server.

In some embodiments, the second validation message directing the client support server to provide the second user with access to the second user account may include information directing the client support server to initiate a second client support session with the second user via the social messaging service provided by the social messaging server.

DETAILED DESCRIPTION

Some aspects of the disclosure relate to dynamically initiating a chat session in response to a banking notification. For example, a bank authentication server may exchange one or more tokens with a social networking server to enable account notifications to be sent to a customer via a social networking messenger service. Subsequently, a customer may respond to a notification received via the social networking service to dynamically initiate a chat session with a bank customer service representative via the social networking messenger service.

FIGS. 1A and 1Bdepict an illustrative computing environment for preventing unauthorized access to secured information systems using tokenized authentication techniques in accordance with one or more example embodiments. Referring toFIG. 1A, computing environment100may include one or more computing devices. For example, computing environment100may include a client portal server120, a client support server130, an administrative computing device140, a social messaging server150, a first client computing device160, a second client computing device170, and a third client computing device180.

Client portal server120may be configured to provide one or more portal interfaces to one or more client devices. For example, client portal server120may be configured to provide a customer portal, such as an online banking portal, to one or more customers of an organization, such as a financial institution, who may use one or more client computing devices to access the portal, such as client computing device160, client computing device170, and client computing device180, as illustrated in greater detail below. In some instances, in addition to being configured to provide an online banking portal associated with a financial institution to one or more customers of the financial institution and/or their associated computing devices, client portal server120also may be configured to provide a mobile banking portal associated with the financial institution to various customers of the financial institution and/or their associated mobile computing devices. Such portals may, for instance, provide customers of the financial institution with access to financial account information (e.g., account balance information, account statements, recent transaction history information, or the like) and/or may provide customers of the financial institution with menus, controls, and/or other options to schedule and/or execute various transactions (e.g., online bill pay transactions, person-to-person funds transfer transactions, or the like).

Client support server130may be configured to initiate and/or provide one or more client support sessions, as illustrated in greater detail below. For example, client support server130may include and/or integrate with one or more client support servers and/or devices, such as one or more customer service representative devices used by one or more customer service representatives of an organization (which may, e.g., be a financial institution operating client portal server120), to connect one or more customers of the organization with one or more customer service representatives of the organization via one or more chat sessions and/or other client support sessions.

Administrative computing device140may be configured to provide one or more interfaces that allow for configuration and management of one or more other computing devices and/or computer systems included in computing environment100. Social messaging server150may be configured to provide a social messaging service, as illustrated in greater detail below. For example, social messaging server150may be operated by and/or otherwise associated with a social networking service (which may, e.g., be different from and/or not associated with a financial institution and/or other organization operating client portal server120). Social messaging server150may, for instance, provide one or more social messaging user interfaces to various users and/or user devices, such as client computing device160, client computing device170, and/or client computing device180, as illustrated in greater detail below.

Client computing device160may be configured to be used by a first customer of an organization, such as a financial institution. In some instances, client computing device160may, for example, be registered with the organization and/or one or more computer systems in computing environment100, such that the organization and/or the one or more computer systems maintain one or more records linking client computing device160to the first customer of the organization, as illustrated in greater detail below. Client computing device170may be configured to be used by a second customer of the organization (who may, e.g., be different from the first customer of the organization). In some instances, client computing device170may, for example, be registered with the organization and/or one or more computer systems in computing environment100, such that the organization and/or the one or more computer systems maintain one or more records linking client computing device170to the second customer of the organization, as illustrated in greater detail below. Client computing device180may be configured to be used by a third customer of the organization (who may, e.g., be different from the first customer of the organization and the second customer of the organization). In some instances, client computing device180may, for example, be registered with the organization and/or one or more computer systems in computing environment100, such that the organization and/or the one or more computer systems maintain one or more records linking client computing device180to the third customer of the organization, as illustrated in greater detail below.

In one or more arrangements, client portal server120, client support server130, administrative computing device140, social messaging server150, client computing device160, client computing device170, and client computing device180may be any type of computing device capable of receiving a user interface, receiving input via the user interface, and communicating the received input to one or more other computing devices. For example, client portal server120, client support server130, administrative computing device140, social messaging server150, client computing device160, client computing device170, and client computing device180may, in some instances, be and/or include server computers, desktop computers, laptop computers, tablet computers, smart phones, or the like that may include one or more processors, memories, communication interfaces, storage devices, and/or other components. As noted above, and as illustrated in greater detail below, any and/or all of client portal server120, client support server130, administrative computing device140, social messaging server150, client computing device160, client computing device170, and client computing device180may, in some instances, be special-purpose computing devices configured to perform specific functions.

Computing environment100also may include one or more computing platforms. For example, computing environment100may include client authentication computing platform110. As illustrated in greater detail below, client authentication computing platform110may include one or more computing devices configured to perform one or more of the functions described herein. For example, client authentication computing platform110may include one or more computers (e.g., laptop computers, desktop computers, servers, server blades, or the like).

Computing environment100also may include one or more networks, which may interconnect one or more of client authentication computing platform110, client portal server120, client support server130, administrative computing device140, social messaging server150, client computing device160, client computing device170, and client computing device180. For example, computing environment100may include public network190and private network195. Private network195and/or public network190may include one or more sub-networks (e.g., local area networks (LANs), wide area networks (WANs), or the like). Private network195may be associated with a particular organization (e.g., a corporation, financial institution, educational institution, governmental institution, or the like) and may interconnect one or more computing devices associated with the organization. For example, client authentication computing platform110, client portal server120, client support server130, and administrative computing device140may be associated with an organization (e.g., a financial institution), and private network195may be associated with and/or operated by the organization, and may include one or more networks (e.g., LANs, WANs, virtual private networks (VPNs), or the like) that interconnect client authentication computing platform110, client portal server120, client support server130, and administrative computing device140and one or more other computing devices and/or computer systems that are used by, operated by, and/or otherwise associated with the organization. Public network190may connect private network195and/or one or more computing devices connected thereto (e.g., client authentication computing platform110, client portal server120, client support server130, and administrative computing device140) with one or more networks and/or computing devices that are not associated with the organization. For example, social messaging server150, client computing device160, client computing device170, and client computing device180might not be associated with an organization that operates private network195(e.g., because social messaging server150, client computing device160, client computing device170, and client computing device180may be owned, operated, and/or serviced by one or more entities different from the organization that operates private network195, such as one or more customers of the organization and/or vendors of the organization, rather than being owned and/or operated by the organization itself or an employee or affiliate of the organization), and public network190may include one or more networks (e.g., the internet) that connect social messaging server150, client computing device160, client computing device170, and client computing device180to private network195and/or one or more computing devices connected thereto (e.g., client authentication computing platform110, client portal server120, client support server130, and administrative computing device140).

Referring toFIG. 1B, client authentication computing platform110may include one or more processors111, memory112, and communication interface115. A data bus may interconnect processor(s)111, memory112, and communication interface115. Communication interface115may be a network interface configured to support communication between client authentication computing platform110and one or more networks (e.g., private network195, public network190, or the like). Memory112may include one or more program modules having instructions that when executed by processor(s)111cause client authentication computing platform110to perform one or more functions described herein and/or one or more databases that may store and/or otherwise maintain information which may be used by such program modules and/or processor(s)111. In some instances, the one or more program modules and/or databases may be stored by and/or maintained in different memory units of client authentication computing platform110and/or by different computing devices that may form and/or otherwise make up client authentication computing platform110. For example, memory112may have, store, and/or include a client authentication module113and a client authentication database114. Client authentication module113may have instructions that direct and/or cause client authentication computing platform110to authenticate one or more users and/or devices using tokenized authentication techniques and/or to perform other functions, as discussed in greater detail below. Client authentication database114may store information used by client authentication module113and/or client authentication computing platform110in authenticating one or more users and/or devices using tokenized authentication techniques and/or in performing other functions.

FIGS. 2A-2Ldepict an illustrative event sequence for preventing unauthorized access to secured information systems using tokenized authentication techniques in accordance with one or more example embodiments. Referring toFIG. 2A, at step201, client computing device160may register with client authentication computing platform110. For example, in registering with client authentication computing platform110at step201, client computing device160may send, to client authentication computing platform110, registration information identifying a specific user account associated with a social messaging service provided by social messaging server150. The user account may, for example, be linked to and/or used by a user of client computing device160for communicating via the social messaging service provided by social messaging server150. At step202, client authentication computing platform110may store registration information. For example, in storing registration information at step202, client authentication computing platform110may store user account information associated with one or more users of client computing device160, device information associated with client computing device160, and/or the like, including some or all of the information received from client computing device160(e.g., during registration at step201).

At step203, client authentication computing platform110may register with social messaging server150. For example, at step203, client authentication computing platform110may register with social messaging server150based on client computing device160registering with client authentication computing platform110, as this may enable client authentication computing platform110to obtain and/or exchange user account information, device information, and/or other information associated with client computing device160and/or a social messaging service account used by a user of client computing device160with social messaging server150. For instance, in registering with social messaging server150at step203, client authentication computing platform110may receive one or more tokens and/or other information from social messaging server150, and the one or more tokens and/or other information received from social messaging server150may be associated with one or more user accounts linked to client computing device160(which may, e.g., include a client portal user account associated with client portal server120and linked to client computing device160, as well as a social messaging service user account associated with social messaging server150and linked to client computing device160).

At step204, client authentication computing platform110may store token information. For example, at step204, client authentication computing platform110may store token information that enables client authentication computing platform110to authenticate social messaging server150and/or enables social messaging server150to authenticate client authentication computing platform110, so that client authentication computing platform110and social messaging server150are able to exchange information associated with client computing device160and/or one or more user accounts linked to client computing device160(e.g., a client portal user account associated with client portal server120and linked to client computing device160, a social messaging service user account associated with social messaging server150and linked to client computing device160). For instance, both client authentication computing platform110and social messaging server150may maintain tokens enabling them to authenticate each other and individual users to secured sessions. In some instances, client authentication computing platform110and social messaging server150may utilize OAUTH standards, and one or more tokens generated and/or maintained by client authentication computing platform110and/or social messaging server150may be defined in accordance with OAUTH standards.

Referring toFIG. 2B, at step205, client portal server120may generate a notification. For example, in generating a notification at step205, client portal server120may generate a client alert for client computing device160and/or a client portal user account linked to client computing device160. The client alert generated by client portal server120for client computing device160and/or the client portal user account linked to client computing device160may, for instance, include information indicating that one or more new account statements and/or other documents are available, one or more special offers are available, unusual account activity has been detected, and/or the like. At step206, client portal server120may send the notification to social messaging server150(e.g., based on one or more user preferences associated with the client portal user account linked to client computing device160indicating that one or more notifications should be sent to client computing device160via a social messaging service provided by social messaging server150). At step207, social messaging server150may send a message to client computing device160. For example, at step207, social messaging server150may send a message to client computing device160via a social messaging service provided by social messaging server150, and the message may include the notification generated by and received from client portal server120.

At step208, client computing device160may present the message received from social messaging server150. For example, in presenting the message received from social messaging server150at step208, client computing device160may display and/or otherwise present a graphical user interface similar to graphical user interface300, which is illustrated inFIG. 3. As seen inFIG. 3, graphical user interface300may be a chat interface associated with a social messaging service provided by social messaging server150. For example, graphical user interface300may include information identifying the source of the message (e.g., “New Message from Company1”), as well as the content of the notification received from client portal server120(e.g., “Hello, <First1Last1>! We wanted to let you know that your most recent statement is now available. Please click here to access your documents” and “If you have any questions, please respond to this message, and we will assist you”). In addition, graphical user interface300may include one or more controls and/or other elements enabling a user of graphical user interface300and/or client computing device160to respond to the message (e.g., a message text entry field, a send button, and/or the like).

Referring toFIG. 2C, at step209, client computing device160may receive chat input. For example, at step209, client computing device160may receive chat input from the user of client computing device160responding to the message presented by client computing device160at step208. As illustrated in greater detail below, the user of client computing device160may respond to the message received from social messaging server150to dynamically start a chat session with a client support representative of an organization (e.g., a financial institution) operating client authentication computing platform110and/or client portal server120. At step210, client computing device160may send the chat input to social messaging server150.

At step211, social messaging server150may send an authentication request to client authentication computing platform110. For example, at step211, social messaging server150may send, to client authentication computing platform110, an authentication request identifying client computing device160and/or a social messaging service user account linked to client computing device160based on receiving the chat input from client computing device160. Client computing device160and/or the user of client computing device160may, for instance, already be authenticated to the social messaging service user account linked to client computing device160and used by the user of client computing device160to communicate via the social messaging service provided by social messaging server150.

At step212, client authentication computing platform110may receive the authentication request from social messaging server150. For example, at step212, client authentication computing platform110may receive, via the communication interface (e.g., communication interface115), and from a social messaging server (e.g., social messaging server150), a request to authenticate a first user to a first user account associated with a client portal provided by a client portal server (e.g., client portal server120).

In some embodiments, the social messaging server may generate the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server based on receiving chat input from a first client computing device associated with the first user. For example, the social messaging server (e.g., social messaging server150) may generate the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server (e.g., client portal server120) based on receiving chat input from a first client computing device associated with the first user (e.g., client computing device160), as illustrated in the example event sequence.

Referring toFIG. 2D, at step213, client authentication computing platform110may send a token request message to social messaging server150. For example, at step213, based on receiving the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server (e.g., client portal server120), client authentication computing platform110may send, via the communication interface (e.g., communication interface115), and to the social messaging server (e.g., social messaging server150), a first authentication token request message. The authentication token request message may, for instance, request a session token from social messaging server150. In some instances, the session token requested from social messaging server150by client authentication computing platform110may be an access token that is created and/or formulated (e.g., by social messaging server150) based on one or more authentication standards, such as OAUTH standards.

At step214, social messaging server150may receive the token request message from client authentication computing platform110. At step215, social messaging server150may send an authentication token to client authentication computing platform110(e.g., in response to the token request message received from client authentication computing platform110at step214). For example, at step215, social messaging server150may send an authentication token to client authentication computing platform110that enables client authentication computing platform110to authenticate a user of the social messaging service provided by social messaging server150in connection with a specific social messaging service session so as to provide the user with access to one or more resources (e.g., maintained by client authentication computing platform110, client portal server120, and/or client support server130) in a specific client portal session and/or client support session. In this way, and as illustrated in greater detail below, the user's authentication status with respect to a social messaging user account on the social messaging service provided by social messaging server150may be carried over to a client support session (which may, e.g., be provided by client support server130) involving the user's client portal user account (which may, e.g., be used by the user to access to a client portal provided by client portal server120).

At step216, client authentication computing platform110may receive the authentication token from social messaging server150. For example, at step216, client authentication computing platform110may receive, via the communication interface (e.g., communication interface115), and from the social messaging server (e.g., social messaging server150), a first authentication token. The authentication token (which may, e.g., be received by client authentication computing platform110at step216) may, for instance, be a session token and/or may include information identifying a social messaging service user account associated with the authentication request (e.g., identifying a social messaging service user account associated with client computing device160), information identifying a client portal user account associated with the authentication request (e.g., identifying a client portal user account associated with client computing device160), information identifying a device associated with the authentication request (e.g., identifying client computing device160, such as a device name, device identifier, network address, and/or the like), one or more keys, certificates, and/or unique identifiers, and/or other information.

In some embodiments, the first authentication token received from the social messaging server may include information indicating that the first user is authenticated to a first social messaging service account associated with a social messaging service provided by the social messaging server. For example, the first authentication token received from the social messaging server (e.g., social messaging server150) may include information indicating that the first user is authenticated to a first social messaging service account associated with a social messaging service provided by the social messaging server (e.g., social messaging server150).

Referring toFIG. 2E, at step217, client authentication computing platform110may validate the authentication token received from social messaging server150. For example, at step217, client authentication computing platform110may validate the first authentication token received from the social messaging server (e.g., social messaging server150). In validating the first authentication token received from the social messaging server (e.g., social messaging server150), client authentication computing platform110may, for instance, determine whether and/or confirm that the first authentication token received from the social messaging server (e.g., social messaging server150) is valid based on the contents of the first authentication token received from the social messaging server (e.g., social messaging server150). If client authentication computing platform110determines that the first authentication token received from the social messaging server (e.g., social messaging server150) is not valid, client authentication computing platform110may generate and/or send one or more error messages, and the event sequence may end. Otherwise, if client authentication computing platform110determines that the first authentication token received from the social messaging server (e.g., social messaging server150) is valid, the example event sequence may continue as illustrated.

At step218, client authentication computing platform110may generate a validation message (e.g., based on validating the authentication token received from social messaging server150at step217). For example, at step218, based on validating the first authentication token received from the social messaging server (e.g., social messaging server150), client authentication computing platform110may generate a first validation message directing a client support server (e.g., client support server130) to provide the first user with access to the first user account. As illustrated in greater detail below, the validation message directing the client support server (e.g., client support server130) to provide the user with access to the user account (which may, e.g., be generated by client authentication computing platform110and sent by client authentication computing platform110to client support server130) may cause the client support server (e.g., client support server130) to initiate a client support session with the user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

In some embodiments, the first validation message directing the client support server to provide the first user with access to the first user account may include information indicating that the first user has been authenticated to the first user account based on the first authentication token received from the social messaging server. For example, the first validation message directing the client support server (e.g., client support server130) to provide the first user with access to the first user account may include information indicating that the first user has been authenticated to the first user account based on the first authentication token received from the social messaging server (e.g., social messaging server150).

In some embodiments, the first validation message directing the client support server to provide the first user with access to the first user account may include information directing the client support server to initiate a first client support session with the first user via the social messaging service provided by the social messaging server. For example, the first validation message directing the client support server (e.g., client support server130) to provide the first user with access to the first user account may include information directing the client support server (e.g., client support server130) to initiate a first client support session with the first user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

At step219, client authentication computing platform110may send the validation message to client support server130. For example, at step219, client authentication computing platform110may send, via the communication interface (e.g., communication interface115), and to the client support server (e.g., client support server130), the first validation message directing the client support server (e.g., client support server130) to provide the first user with access to the first user account. In directing the client support server (e.g., client support server130) to provide the user with access to the user account, the validation message generated and sent by client authentication computing platform110to the client support server (e.g., client support server130) may also direct the client support server (e.g., client support server130) to initiate a client support session with the user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

At step220, client support server130may receive the validation message from client authentication computing platform110. Referring toFIG. 2F, at step221, client support server130may select a client support endpoint (e.g., based on receiving the validation message from client authentication computing platform110). For instance, client support server130may select a particular client support computing device and/or a particular client support representative associated with a particular client support computing device for initiating a client support session with the user of client computing device160via the social messaging service provided by the social messaging server (e.g., social messaging server150). At step222, client support server130may connect the selected client support endpoint with social messaging server150. For example, at step222, client support server130may connect the selected client support endpoint with social messaging server150by establishing one or more network connections between the selected client support endpoint and social messaging server150.

At step223, client support server130may initiate a client support session. For example, at step223, client support server130may initiate a client support session by directing and/or connecting the selected client support endpoint to a specific chat session associated with client computing device160and/or a user account linked to client computing device160via the social messaging service provided by the social messaging server (e.g., social messaging server150). For instance, client support server130may direct and/or connect the selected client support endpoint to the chat session initiated when the user of client computing device160responded to the message presented at step208with the chat input received by social messaging server150at step210.

At step224, client computing device160may present one or more user interfaces and/or other information associated with the client support session. For example, in presenting one or more user interfaces and/or other information associated with the client support session at step224, client computing device160may display and/or otherwise present a graphical user interface similar to graphical user interface400, which is illustrated inFIG. 4. As seen inFIG. 4, graphical user interface400may be a chat interface associated with a social messaging service provided by social messaging server150. For example, graphical user interface400may include information identifying the chat (e.g., “Chat with Company1”) as well as the chat messages that may comprise the contents of the client support session (e.g., “Hi, I have a question about my statement” and “Hello <First1>. I'm<First2>. How can I help you today?”). In addition, graphical user interface400may include one or more controls and/or other elements enabling a user of graphical user interface400and/or client computing device160to provide chat input to participate in the client support session and/or otherwise respond to messages received from the selected client support endpoint via the social messaging service provided by social messaging server150(e.g., a message text entry field, a send button, and/or the like).

Subsequently, one or more steps of the event sequence discussed above may be repeated by client authentication computing platform110and/or the other systems discussed above in authenticating another user to another user account associated with the client portal provided by client portal server120. Although such steps are illustrated separately and following the steps performed with respect to authenticating the first user, various steps may be performed in a different order, such that client authentication computing platform110may, for instance, authenticate multiple users simultaneously as social messaging server150receives chat input from different users and/or devices responding to different notifications and/or messages originating from client portal server120and/or sent via the social messaging service provided by social messaging server150.

Referring toFIG. 2G, at step225, client computing device170may register with client authentication computing platform110. For example, in registering with client authentication computing platform110at step225, client computing device170may send, to client authentication computing platform110, registration information identifying a specific user account associated with the social messaging service provided by social messaging server150. The user account may, for example, be linked to and/or used by a user of client computing device170for communicating via the social messaging service provided by social messaging server150. At step226, client authentication computing platform110may store registration information. For example, in storing registration information at step226, client authentication computing platform110may store user account information associated with one or more users of client computing device170, device information associated with client computing device170, and/or the like, including some or all of the information received from client computing device170(e.g., during registration at step225).

At step227, client authentication computing platform110may register with social messaging server150. For example, at step227, client authentication computing platform110may register with social messaging server150based on client computing device170registering with client authentication computing platform110, as this may enable client authentication computing platform110to obtain and/or exchange user account information, device information, and/or other information associated with client computing device170and/or a social messaging service account used by a user of client computing device170with social messaging server150. For instance, in registering with social messaging server150at step227, client authentication computing platform110may receive one or more tokens and/or other information from social messaging server150, and the one or more tokens and/or other information received from social messaging server150may be associated with one or more user accounts linked to client computing device170(which may, e.g., include a client portal user account associated with client portal server120and linked to client computing device170, as well as a social messaging service user account associated with social messaging server150and linked to client computing device170).

At step228, client authentication computing platform110may store token information. For example, at step228, client authentication computing platform110may store token information that enables client authentication computing platform110to authenticate social messaging server150and/or enables social messaging server150to authenticate client authentication computing platform110, so that client authentication computing platform110and social messaging server150are able to exchange information associated with client computing device170and/or one or more user accounts linked to client computing device170(e.g., a client portal user account associated with client portal server120and linked to client computing device170, a social messaging service user account associated with social messaging server150and linked to client computing device170). For instance, both client authentication computing platform110and social messaging server150may maintain tokens enabling them to authenticate each other and individual users to secured sessions. In some instances, client authentication computing platform110and social messaging server150may utilize OAUTH standards, and one or more tokens generated and/or maintained by client authentication computing platform110and/or social messaging server150may be defined in accordance with OAUTH standards.

Referring toFIG. 2H, at step229, client portal server120may generate a notification. For example, in generating a notification at step229, client portal server120may generate a client alert for client computing device170and/or a client portal user account linked to client computing device170. The client alert generated by client portal server120for client computing device170and/or the client portal user account linked to client computing device170may, for instance, include information indicating that one or more new account statements and/or other documents are available, one or more special offers are available, unusual account activity has been detected, and/or the like. At step230, client portal server120may send the notification to social messaging server150(e.g., based on one or more user preferences associated with the client portal user account linked to client computing device170indicating that one or more notifications should be sent to client computing device170via a social messaging service provided by social messaging server150). At step231, social messaging server150may send a message to client computing device170. For example, at step231, social messaging server150may send a message to client computing device170via a social messaging service provided by social messaging server150, and the message may include the notification generated by and received from client portal server120.

At step232, client computing device170may present the message received from social messaging server150. For example, in presenting the message received from social messaging server150at step232, client computing device170may display and/or otherwise present a graphical user interface similar to graphical user interface500, which is illustrated inFIG. 5. As seen inFIG. 5, graphical user interface500may be a chat interface associated with a social messaging service provided by social messaging server150. For example, graphical user interface500may include information identifying the source of the message (e.g., “New Message from Company1”), as well as the content of the notification received from client portal server120(e.g., “Hello, <First2Last2>! We wanted to let you know that a new special offer is now available. Please click here to learn more” and “If you have any questions, please respond to this message, and we will assist you”). In addition, graphical user interface500may include one or more controls and/or other elements enabling a user of graphical user interface500and/or client computing device170to respond to the message (e.g., a message text entry field, a send button, and/or the like).

Referring toFIG. 2I, at step232, client computing device170may receive chat input. For example, at step232, client computing device170may receive chat input from the user of client computing device170responding to the message presented by client computing device170at step232. As illustrated in greater detail below, the user of client computing device170may respond to the message received from social messaging server150to dynamically start a chat session with a client support representative of an organization (e.g., a financial institution) operating client authentication computing platform110and/or client portal server120. At step234, client computing device170may send the chat input to social messaging server150.

At step235, social messaging server150may send an authentication request to client authentication computing platform110. For example, at step235, social messaging server150may send, to client authentication computing platform110, an authentication request identifying client computing device170and/or a social messaging service user account linked to client computing device170based on receiving the chat input from client computing device170. Client computing device170and/or the user of client computing device170may, for instance, already be authenticated to the social messaging service user account linked to client computing device170and used by the user of client computing device170to communicate via the social messaging service provided by social messaging server150.

At step236, client authentication computing platform110may receive the authentication request from social messaging server150. For example, at step236, client authentication computing platform110may receive, via the communication interface (e.g., communication interface115), and from the social messaging server (e.g., social messaging server150), a request to authenticate a second user to a second user account associated with the client portal provided by the client portal server (e.g., client portal server120).

In some embodiments, the social messaging server may generate the request to authenticate the second user to the second user account associated with the client portal provided by the client portal server based on receiving chat input from a second client computing device associated with the second user. For example, the social messaging server (e.g., social messaging server150) may generate the request to authenticate the second user to the second user account associated with the client portal provided by the client portal server (e.g., client portal server120) based on receiving chat input from a second client computing device associated with the second user (e.g., client computing device170), as illustrated in the example event sequence.

Referring toFIG. 2J, at step237, client authentication computing platform110may send a token request message to social messaging server150. For example, at step237, based on receiving the request to authenticate the second user to the second user account associated with the client portal provided by the client portal server (e.g., client portal server120), client authentication computing platform110may send, via the communication interface (e.g., communication interface115), and to the social messaging server (e.g., social messaging server150), a second authentication token request message. The authentication token request message may, for instance, request a session token from social messaging server150. In some instances, the session token requested from social messaging server150by client authentication computing platform110may be an access token that is created and/or formulated (e.g., by social messaging server150) based on one or more authentication standards, such as OAUTH standards.

At step238, social messaging server150may receive the token request message from client authentication computing platform110. At step239, social messaging server150may send an authentication token to client authentication computing platform110(e.g., in response to the token request message received from client authentication computing platform110at step238). For example, at step239, social messaging server150may send an authentication token to client authentication computing platform110that enables client authentication computing platform110to authenticate a user of the social messaging service provided by social messaging server150in connection with a specific social messaging service session so as to provide the user with access to one or more resources (e.g., maintained by client authentication computing platform110, client portal server120, and/or client support server130) in a specific client portal session and/or client support session. In this way, and as illustrated in greater detail below, the user's authentication status with respect to a social messaging user account on the social messaging service provided by social messaging server150may be carried over to a client support session (which may, e.g., be provided by client support server130) involving the user's client portal user account (which may, e.g., be used by the user to access to a client portal provided by client portal server120).

At step240, client authentication computing platform110may receive the authentication token from social messaging server150. For example, at step240, client authentication computing platform110may receive, via the communication interface (e.g., communication interface115), and from the social messaging server (e.g., social messaging server150), a second authentication token. The authentication token (which may, e.g., be received by client authentication computing platform110at step240) may, for instance, be a session token and/or may include information identifying a social messaging service user account associated with the authentication request (e.g., identifying a social messaging service user account associated with client computing device170), information identifying a client portal user account associated with the authentication request (e.g., identifying a client portal user account associated with client computing device170), information identifying a device associated with the authentication request (e.g., identifying client computing device170, such as a device name, device identifier, network address, and/or the like), one or more keys, certificates, and/or unique identifiers, and/or other information.

In some embodiments, the second authentication token received from the social messaging server may include information indicating that the second user is authenticated to a second social messaging service account associated with the social messaging service provided by the social messaging server. For example, the second authentication token received from the social messaging server (e.g., social messaging server150) may include information indicating that the second user is authenticated to a second social messaging service account associated with the social messaging service provided by the social messaging server (e.g., social messaging server150).

Referring toFIG. 2K, at step241, client authentication computing platform110may validate the authentication token received from social messaging server150. For example, at step241, client authentication computing platform110may validate the second authentication token received from the social messaging server (e.g., social messaging server150). In validating the second authentication token received from the social messaging server (e.g., social messaging server150), client authentication computing platform110may, for instance, determine whether and/or confirm that the second authentication token received from the social messaging server (e.g., social messaging server150) is valid based on the contents of the second authentication token received from the social messaging server (e.g., social messaging server150). If client authentication computing platform110determines that the second authentication token received from the social messaging server (e.g., social messaging server150) is not valid, client authentication computing platform110may generate and/or send one or more error messages, and the event sequence may end. Otherwise, if client authentication computing platform110determines that the second authentication token received from the social messaging server (e.g., social messaging server150) is valid, the example event sequence may continue as illustrated.

At step242, client authentication computing platform110may generate a validation message (e.g., based on validating the authentication token received from social messaging server150at step241). For example, at step242, based on validating the second authentication token received from the social messaging server (e.g., social messaging server150), client authentication computing platform110may generate a second validation message directing the client support server (e.g., client support server130) to provide the second user with access to the second user account. As illustrated in greater detail below, the validation message directing the client support server (e.g., client support server130) to provide the user with access to the user account (which may, e.g., be generated by client authentication computing platform110and sent by client authentication computing platform110to client support server130) may cause the client support server (e.g., client support server130) to initiate a client support session with the user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

In some embodiments, the second validation message directing the client support server to provide the second user with access to the second user account may include information indicating that the second user has been authenticated to the second user account based on the second authentication token received from the social messaging server. For example, the second validation message directing the client support server (e.g., client support server130) to provide the second user with access to the second user account may include information indicating that the second user has been authenticated to the second user account based on the second authentication token received from the social messaging server (e.g., social messaging server150).

In some embodiments, the second validation message directing the client support server to provide the second user with access to the second user account may include information directing the client support server to initiate a second client support session with the second user via the social messaging service provided by the social messaging server. For example, the second validation message directing the client support server (e.g., client support server130) to provide the second user with access to the second user account may include information directing the client support server (e.g., client support server130) to initiate a second client support session with the second user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

At step243, client authentication computing platform110may send the validation message to client support server130. For example, at step243, client authentication computing platform110may send, via the communication interface (e.g., communication interface115), and to the client support server (e.g., client support server130), the second validation message directing the client support server (e.g., client support server130) to provide the second user with access to the second user account. In directing the client support server (e.g., client support server130) to provide the user with access to the user account, the validation message generated and sent by client authentication computing platform110to the client support server (e.g., client support server130) may also direct the client support server (e.g., client support server130) to initiate a client support session with the user via the social messaging service provided by the social messaging server (e.g., social messaging server150).

At step244, client support server130may receive the validation message from client authentication computing platform110. Referring toFIG. 2L, at step245, client support server130may select a client support endpoint (e.g., based on receiving the validation message from client authentication computing platform110). For instance, client support server130may select a particular client support computing device and/or a particular client support representative associated with a particular client support computing device for initiating a client support session with the user of client computing device170via the social messaging service provided by the social messaging server (e.g., social messaging server150). At step246, client support server130may connect the selected client support endpoint with social messaging server150. For example, at step246, client support server130may connect the selected client support endpoint with social messaging server150by establishing one or more network connections between the selected client support endpoint and social messaging server150.

At step247, client support server130may initiate a client support session. For example, at step247, client support server130may initiate a client support session by directing and/or connecting the selected client support endpoint to a specific chat session associated with client computing device170and/or a user account linked to client computing device170via the social messaging service provided by the social messaging server (e.g., social messaging server150). For instance, client support server130may direct and/or connect the selected client support endpoint to the chat session initiated when the user of client computing device170responded to the message presented at step232with the chat input received by social messaging server150at step234.

At step248, client computing device170may present one or more user interfaces and/or other information associated with the client support session. For example, in presenting one or more user interfaces and/or other information associated with the client support session at step248, client computing device170may display and/or otherwise present a graphical user interface similar to graphical user interface600, which is illustrated inFIG. 6. As seen inFIG. 6, graphical user interface600may be a chat interface associated with a social messaging service provided by social messaging server150. For example, graphical user interface600may include information identifying the chat (e.g., “Chat with Company1”) as well as the chat messages that may comprise the contents of the client support session (e.g., “Hi, I have a question about the offer” and “Hello <First2>. I'm<First3>. How can I help you today?”). In addition, graphical user interface600may include one or more controls and/or other elements enabling a user of graphical user interface600and/or client computing device170to provide chat input to participate in the client support session and/or otherwise respond to messages received from the selected client support endpoint via the social messaging service provided by social messaging server150(e.g., a message text entry field, a send button, and/or the like).

FIG. 7depicts an illustrative method for preventing unauthorized access to secured information systems using tokenized authentication techniques in accordance with one or more example embodiments. Referring toFIG. 7, at step705, a computing platform having at least one processor, a memory, and a communication interface may receive, via the communication interface, and from a social messaging server, a request to authenticate a first user to a first user account associated with a client portal provided by a client portal server. At step710, based on receiving the request to authenticate the first user to the first user account associated with the client portal provided by the client portal server, the computing platform may send, via the communication interface, and to the social messaging server, a first authentication token request message. At step715, the computing platform may receive, via the communication interface, and from the social messaging server, a first authentication token. At step720, the computing platform may validate the first authentication token received from the social messaging server. At step725, based on validating the first authentication token received from the social messaging server, the computing platform may generate a first validation message directing a client support server to provide the first user with access to the first user account. At step730, the computing platform may send, via the communication interface, and to the client support server, the first validation message directing the client support server to provide the first user with access to the first user account.