Using Personalized URL for Advanced Login Security

• US 20150020178A1
• Filed: 07/12/2013
• Published: 01/15/2015
• Est. Priority Date: 07/12/2013
• Status: Abandoned Application

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Nachman, David E., Nassar, Nader M., Nassar, Tamer M., Grunin, Galina
• Application Number:
  US13/940,492
• Publication Number:
  US 20150020178A1
• Time in Patent Office: Days
• US Class Current: 726/7
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

Techniques for advanced login security using personalized, user-specific urls are provided. In one aspect, a method for authenticating a user is provided. The method includes the following steps. A personalized login url and credentials (e.g., username and password) are stored for the user. Upon receipt of a login url from the user, it is verified whether the login url matches the personalized url stored for the user. If the login url matches the personalized url for the user, then the user is provided with a user-specific login page where the user can enter credentials, otherwise access is denied. The user is authenticated only if the credentials the user enters match the credentials stored for the user, otherwise denying access.

Claims

1. A method for authenticating a user, the method comprising the steps of:

storing a personalized login url and credentials for the user;

upon receipt of a login url from the user, verifying whether the login url matches the personalized url stored for the user;

if the login url matches the personalized url for the user, then providing the user with a user-specific login page where the user can enter credentials, otherwise denying access; and

authenticating the user only if the credentials the user enters match the credentials stored for the user, otherwise denying access.

2. The method of claim 1, wherein access to the user-specific login page is needed in order to access credential fields for the user to enter the credentials.

3. The method of claim 1, further comprising the step of:

creating an account for the user.

4. The method of claim 3, wherein the step of creating the account for the user comprises the steps of:

prompting the user to enter a suggested personalized login url;

determining if the suggested personalized login url is valid; and

if the suggested personalized login url is valid, then assigning the suggested personalized login url as the personalized login url for the user, otherwise prompting the user to enter a different suggested personalized login url.

5. The method of claim 4, further comprising the step of:

determining if the suggested personalized login url is valid based on security guidelines.

6. The method of claim 4, wherein the suggested personalized login url is invalid if the suggested personalized login url is being used by another user.

7. The method of claim 1, further comprising the steps of:

upon receipt of the login url from the user, consulting a database of personalized login urls, users and credentials to determine whether the login url matches one of the personalized login urls in the database; and

if the login url matches a given one of the personalized login urls in the database, then providing the user with the user-specific login page where the user can enter credentials, otherwise denying access.

8. The method of claim 7, further comprising the steps of:

authenticating the user only if the credentials the user enters match the credentials stored for the given personalized login url in the database, otherwise denying access.

9-20. -20. (canceled)