Authenticating Clients Using Tokens

• US 20170295159A1
• Filed: 04/06/2016
• Published: 10/12/2017
• Est. Priority Date: 04/06/2016
• Status: Abandoned Application

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Arora, Ashish, Jalota, Vikram, Keys, Andrew T.
• Application Number:
  US15/091,754
• Publication Number:
  US 20170295159A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A computing platform may receive, from a client communication server, a first token request requesting a token for a first client. The computing platform may generate a first token linked to a first record associated with the first client. Subsequently, the computing platform may send, to the client communication server, the first token linked to the first record associated with the first client. Thereafter, the computing platform may receive, from a client portal server, a first token validation request comprising the first token linked to the first record associated with the first client, and may validate the first token linked to the first record associated with the first client. Based on validating the first token, the computing platform may send, to the client portal server, a first token validation message directing the client portal server to provide the first record associated with the first client to the first client.

Claims

1. A computing platform, comprising:

at least one processor;

a communication interface communicatively coupled to the at least one processor; and

memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to;

receive, via the communication interface, and from a client communication server, a first token request requesting a token for a first client;

based on receiving the first token request requesting the token for the first client, generate a first token linked to a first record associated with the first client;

send, via the communication interface, and to the client communication server, the first token linked to the first record associated with the first client;

receive, via the communication interface, and from a client portal server, a first token validation request comprising the first token linked to the first record associated with the first client;

based on receiving the first token validation request comprising the first token linked to the first record associated with the first client, validate the first token linked to the first record associated with the first client; and

based on validating the first token linked to the first record associated with the first client, send, via the communication interface, and to the client portal server, a first token validation message directing the client portal server to provide the first record associated with the first client to the first client.

2. The computing platform of claim 1, wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

prior to generating the first token linked to the first record associated with the first client, evaluate one or more authentication security factors associated with the first client to determine to generate the first token linked to the first record associated with the first client.

3. The computing platform of claim 2, wherein evaluating the one or more authentication security factors associated with the first client comprises evaluating one or more of device login history information associated with the first client, network address login history information associated with the first client, or login trend information associated with the first client.

4. The computing platform of claim 2, wherein the first record comprises user account details information associated with the first client.

5. The computing platform of claim 2, wherein the client communication server is configured to send one or more messages to one or more client devices.

6. The computing platform of claim 2, wherein the client portal server is configured to provide one or more client portal interfaces to one or more client devices.

7. The computing platform of claim 2, wherein validating the first token linked to the first record associated with the first client comprises:

sending, via the communication interface, and to a registered device associated with the first client, a one-time passcode; and

validating one-time passcode input received from the client portal server.

8. The computing platform of claim 2, wherein validating the first token linked to the first record associated with the first client comprises:

sending, via the communication interface, and to the client portal server, one or more security questions associated with the first client; and

validating security question response input received from the client portal server.

9. The computing platform of claim 2, wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

receive, via the communication interface, and from the client communication server, a second token request requesting a token for a second client different from the first client;

based on receiving the second token request requesting the token for the second client, generate a second token linked to a second record associated with the second client;

send, via the communication interface, and to the client communication server, the second token linked to the second record associated with the second client;

receive, via the communication interface, and from the client portal server, a second token validation request comprising the second token linked to the second record associated with the second client;

based on receiving the second token validation request comprising the second token linked to the second record associated with the second client, validate the second token linked to the second record associated with the second client; and

based on validating the second token linked to the second record associated with the second client, send, via the communication interface, and to the client portal server, a second token validation message directing the client portal server to provide the second record associated with the second client to the second client.

10. The computing platform of claim 9, wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

prior to generating the second token linked to the second record associated with the second client, evaluate one or more authentication security factors associated with the second client to determine to generate the second token linked to the second record associated with the second client.

11. The computing platform of claim 10, wherein evaluating the one or more authentication security factors associated with the second client comprises evaluating one or more of device login history information associated with the second client, network address login history information associated with the second client, or login trend information associated with the second client.

12. The computing platform of claim 10, wherein the second record comprises user account details information associated with the second client.

13. The computing platform of claim 10, wherein validating the second token linked to the second record associated with the second client comprises:

sending, via the communication interface, and to a registered device associated with the second client, a one-time passcode; and

validating one-time passcode input received from the client portal server.

14. The computing platform of claim 10, wherein validating the second token linked to the second record associated with the second client comprises:

sending, via the communication interface, and to the client portal server, one or more security questions associated with the second client; and

validating security question response input received from the client portal server.

15. A method, comprising:

at a computing platform comprising at least one processor, memory, and a communication interface;

receiving, by the at least one processor, via the communication interface, and from a client communication server, a first token request requesting a token for a first client;

based on receiving the first token request requesting the token for the first client, generating, by the at least one processor, a first token linked to a first record associated with the first client;

sending, by the at least one processor, via the communication interface, and to the client communication server, the first token linked to the first record associated with the first client;

receiving, by the at least one processor, via the communication interface, and from a client portal server, a first token validation request comprising the first token linked to the first record associated with the first client;

based on receiving the first token validation request comprising the first token linked to the first record associated with the first client, validating, by the at least one processor, the first token linked to the first record associated with the first client; and

based on validating the first token linked to the first record associated with the first client, sending, by the at least one processor, via the communication interface, and to the client portal server, a first token validation message directing the client portal server to provide the first record associated with the first client to the first client.

16. The method of claim 15, comprising:

prior to generating the first token linked to the first record associated with the first client, evaluating, by the at least one processor, one or more authentication security factors associated with the first client to determine to generate the first token linked to the first record associated with the first client.

17. The method of claim 16, wherein evaluating the one or more authentication security factors associated with the first client comprises evaluating one or more of device login history information associated with the first client, network address login history information associated with the first client, or login trend information associated with the first client.

18. The method of claim 16, wherein the first record comprises user account details information associated with the first client.

19. The method of claim 16,

wherein the client communication server is configured to send one or more messages to one or more client devices, and

wherein the client portal server is configured to provide one or more client portal interfaces to one or more client devices.

20. One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, memory, and a communication interface, cause the computing platform to:

receive, via the communication interface, and from a client communication server, a first token request requesting a token for a first client;

based on receiving the first token request requesting the token for the first client, generate a first token linked to a first record associated with the first client;

send, via the communication interface, and to the client communication server, the first token linked to the first record associated with the first client;

receive, via the communication interface, and from a client portal server, a first token validation request comprising the first token linked to the first record associated with the first client;

based on receiving the first token validation request comprising the first token linked to the first record associated with the first client, validate the first token linked to the first record associated with the first client; and

based on validating the first token linked to the first record associated with the first client, send, via the communication interface, and to the client portal server, a first token validation message directing the client portal server to provide the first record associated with the first client to the first client.