IP Library Granted Patent US 10,063,543
Granted Patent B2
US 10,063,543 · App. 14/311,911 · Granted Aug 28, 2018

Computer implemented method to prevent attacks against user authentication and computer programs products thereof

Inventors: Jose Maria Alonso Cebrian (Madrid, ES); David Barroso Berrueta (Madrid, ES); Jose Maria Palazon Romero (Madrid, ES); Antonio Guzman Sacristan (Madrid, ES)
Assignee: TELEFONICA DIGITAL ESPANA, S.L.U.
H04L63/0869H04L63/08H04L63/0838H04L63/108
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,063,543
App. No.
14/311,911
Granted
Aug 28, 2018
Kind
B2
Abstract

The computer implemented method comprising: receiving a first server a request in the name of a user to be logged into a service of said first server and authenticating said request by verifying user identification information of said user, wherein a second server in connection with a user computing device with a dedicated program is used for: receiving a request about a status associated to said user; initializing a credential exchange in order to provide mutual authentication; verifying said associated status that has been previously set as valid or as invalid by said user; and sending said associated status to said first server wherein the latter allows the logging of said request or rejects it if said associated status is set as valid or as invalid.

Claims (93)

1. A computer implemented method to prevent attacks against user authentication, the method comprising:

prior to user authentication with a first server, receiving by the first server a login request from a first user in a name of a second user to be logged into a service of the first server;

transmitting, by the first server to a second server, a request for a user status associated with the second user;

in response to transmitting the request, initializing a credential exchange between the first server and the second server to provide mutual authentication, and in response to a successful mutual authentication, verifying the user status associated with the second user that has been previously set as valid or as invalid by the second user and stored in a memory of the second server, and sending, by the second server, the user status to the first server;

receiving, by the first server, the user status and using the received user status to:

authorize the login request from the first user in the name of the second user in response to the user status being set as valid; and

rejecting the login request from the first user in the name of the second user in response to the user status being set as invalid,

wherein in response to the login request being authorized and an operation request from the first user in the name of a second user to perform an operation in the first server using at least a part of resources of the first server:

transmitting, by the first server to the second server, a request for a user status associated with the second user,

initializing a credential exchange between the first server and the second server,

in response to a successful credential exchange, verifying the user status associated with the second user as valid or invalid,

sending, by the second server, the user status to the first server, and

authorizing the operation request in response to the user status being set as valid, and

rejecting the operation request in response to the user status being set as invalid.

2. The computer implemented method according to claim 1 , wherein the request for user status includes a security token that was generated and stored in the first server after a previous successful user account pairing process between the first server and the second server, and

wherein the security token is encrypted.

3. The computer implemented method according to claim 1 , wherein the request for user status includes a unique identifier of the second user.

4. The computer implemented method according to claim 1 , wherein rejecting the login request comprises notifying the second user that the login request is rejected.

5. The computer implemented method according to claim 4 , wherein the notifying comprises one of a sending of a Short Message Service (SMS) message to the second user, a sending an email to the second user, a sending of a message to the second user by a smartphone messenger application, or a highlighting or pushing in a dedicated program of a user computing device from which the login request was received.

6. The computer implemented method according to claim 1 , wherein the received login request is recorded in the first server.

7. The computer implemented method according to claim 1 , wherein the user status is modifiable.

8. The computer implemented method according to claim 1 , wherein the user status if verified based on one or more parameters and the one or more parameters comprise a period of time in which the user status is valid.

9. A non-transitory computer readable medium storing a program causing a computer to execute a method comprising:

prior to user authentication with a first server, receiving by the first server a login request from a first user in a name of a second user to be logged into a service of the first server;

transmitting, by the first server to a second server, a request for a user status associated with the second user;

in response to transmitting the request, initializing a credential exchange between the first server and the second server to provide mutual authentication, and in response to a successful mutual authentication, verifying the user status associated with the second user that has been previously set as valid or as invalid by the second user and stored in a memory of the second server, and sending, by the second server, the user status to the first server;

receiving, by the first server, the user status and using the received user status to:

authorize the login request from the first user in the name of the second user in response to the user status being set as valid; and

rejecting the login request from the first user in the name of the second user in response to the user status being set as invalid,

wherein in response to the login request being authorized and an operation request from the first user in the name of a second user to perform an operation in the first server using at least a part of resources of the first server:

transmitting, by the first server to the second server, a request for a user status associated with the second user,

initializing a credential exchange between the first server and the second server,

in response to a successful credential exchange, verifying the user status associated with the second user as valid or invalid,

sending, by the second server, the user status to the first server, and

authorizing the operation request in response to the user status being set as valid, and

rejecting the operation request in response to the user status being set as invalid.

10. The non-transitory computer readable medium according to claim 9 , wherein the request for user status includes a unique identifier of the second user.

11. The non-transitory computer readable medium according to claim 9 , wherein the login request is received from a mobile phone, a smartphone, a tablet-PC, or a PDA.

12. The non-transitory computer readable medium according to claim 9 , wherein the request for user status includes a security token that was generated and stored in the first server after a previous successful user account pairing process between the first server and the second server, and.

13. The computer implemented method according to claim 1 , wherein the user status is a lock/unlock status set by the second user according to a lock/unlock policy.

14. The non-transitory computer readable medium according to claim 9 , wherein the user status is a lock/unlock status set by the second user according to a lock/unlock policy.

15. The computer implemented method according to claim 2 , wherein the security token links the second user with the first server without including personal information of the second user.

16. The non-transitory computer readable medium according to claim 12 , wherein the security token links the second user with the first server without including personal information of the second user.

17. A computer implemented system comprising:

a first server and a second server,

wherein the first server comprises at least one microprocessor configured to:

prior to user authentication with the first server, receive a login request from a first user in a name of a second user to be logged into a service of the first server;

transmit to the second server a request for a user status associated with the second user;

receive by the first server a request from the second server for credentials of the first server, and transmitting the credentials of the first server to the second server to perform a credential exchange between the first server and the second server;

in response to a successful credential exchange, receive a status resolution of the user status from the second server; and

authorizing the login request of the first user in the name of the second user when the status resolution indicates the user status is valid; and

reject the login request of the first user in the name of the second user when the status resolution indicates the user status is invalid, and

wherein the second server comprises at least one microprocessor configured to:

receive from the first server the request for the user status of the second user;

transmit the request for credentials to the first server, and receive the credentials from the first server;

verify the credentials of the first server;

in response to successfully verifying the credentials of the first server, verify the user status associated with the second user that has been previously set as valid or as invalid by the second user and stored in a memory of the second server, and

in response to verifying the user status, transmit to the first server the status resolution of the user status, the status resolution indicating whether the user status is valid or invalid based on parameters previously set and stored by the user in the second server,

wherein in response to the first server authorizing the login request:

the first server:

transmits to the second server, a request for a user status associated with the second user,

performs a credential exchange with the second server,

in response to a successful credential exchange, receives the user status associated with the second user as valid or invalid,

authorizes the operation request in response to the user status being set as valid, and

rejects the operation request in response to the user status being set as invalid, and the second server:

receives the request for the user status associated with the second server,

performs the credential exchange with the first server,

in response to the successful credential exchange, verifies the user status associated with the second user as valid or invalid, and

sends the verified user status to the first server.

18. A non-transitory computer readable medium comprising a first medium storing a first program, which when executed by a first server computer, causes the first server computer to implement a first method comprising:

prior to user authentication with the first server, receive a login request from a first user in a name of a second user to be logged into a service of the first server;

transmit to the second server a request for a user status associated with the second user;

receive by the first server a request from the second server for credentials of the first server, and transmitting the credentials of the first server to the second server to perform a credential exchange between the first server and the second server;

in response to a successful credential exchange, receive a status resolution of the user status from the second server; and

authorizing the login request of the first user in the name of the second user when the status resolution indicates the user status is valid; and

reject the login request of the first user in the name of the second user when the status resolution indicates the user status is invalid, and

wherein the non-transitory computer readable medium comprises a second medium storing a second program, which when executed by a second server computer, causes the second server computer to implement a second method comprising:

receive from the first server the request for the user status of the second user;

transmit the request for credentials to the first server, and receive the credentials from the first server;

verify the credentials of the first server;

in response to successfully verifying the credentials of the first server, verify the user status associated with the second user that has been previously set as valid or as invalid by the second user and stored in a memory of the second server,

wherein in response to the first server authorizing the login request:

the first method further comprises:

transmitting to the second server, a request for a user status associated with the second user,

performing a credential exchange with the second server,

in response to a successful credential exchange, receiving the user status associated with the second user as valid or invalid,

authorizing the operation request in response to the user status being set as valid, and

rejecting the operation request in response to the user status being set as invalid, and

the second method further comprises:

receiving the request for the user status associated with the second server,

performing the credential exchange with the first server,

in response to the successful credential exchange, verifying the user status associated with the second user as valid or invalid, and

sending the verified user status to the first server.

Assignments (4)
CHANGE OF NAME Recorded Jun 21, 2024
From: TELEFONICA DIGITAL ESPAÑA SL
To: TELEFONICA INNOVACION DIGITAL SL
Reel/Frame 067807/0092 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 12, 2022
From: TELEFONICA CYBERSECURITY TECH S.L.
To: TELEFÓNICA DIGITAL ESPAÑA, S.L.U.
Reel/Frame 061393/0176 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2021
From: TELEFONICA DIGITAL ESPANA, S.L.U.
To: TELEFONICA CYBERSECURITY TECH S.L.
Reel/Frame 055674/0377 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 22, 2014
From: ALONSO CEBRIAN, JOSE MARIA; BARROSO BERRUETA, DAVID; PALAZON ROMERO, JOSE MARIA; GUZMAN SACRISTAN, ANTONIO
To: TELEFONICA DIGITAL ESPANA, S.L.U.
Reel/Frame 034004/0018 →
Priority Claims (1)
EP 13382237 · Jun 24, 2013 · regional
Continuity (1)
Related Publication 20140380453A1 · Dec 25, 2014
Cited By (2)
US 12,483,551 US 12,572,386