Browse Prior Art Database

Short Name History

IP.com Disclosure Number: IPCOM000236908D
Publication Date: 2014-May-21
Document File: 2 page(s) / 42K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to accelerate and simplify the user identification process used by software products and applications that maintain user references. The method is to maintain an alias table with references from the old short name to the new short name.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Short Name History

Many products maintain user references for particular users. The users can come from any third-party security back end, one being a Lightweight Directory Access Protocol (LDAP) repository. A user is identified by some unique short name. The short name may be referenced in the data and used to process information.

If the short name needs to change for any reason in the third party software, then the internal references in the data also must be changed to the new short name value. In large systems, data references might reside in many locations within an application's database; therefore, finding and updating these short names can be time-consuming and complicated.

The novel contribution is a method to minimize the changes to the data by maintaining an alias table with a reference from the old short name to the new short name.

This method is applicable to an application that indirectly references a user via an internal unique ID created for and by the application. The mapping between the internal ID and third party name is stored in a user record and serves two purposes: to insulate the application from a third party change and to accelerate data processing.

The core idea of the method is to use an alias table that tracks the history of the security change (e.g., User A used to be named User B, in Feb/2012). The method applies a scheme to detect change and can use more than one field in the third party software to identify a security principal. The idea is that if one field is changed, then the system can use the other field to search for and identify the new value.

The criteria for the field selection are as follows:

1. One field is a user-friendly, unique, readable short name so the user can easily change this name in the third party software

2. The other field contains an internally generated system Globally Unique Identifier (GUID). This GUID is unique in time/space unless the security credential is deleted and recreated.

The field selections are configurable.

The abstraction is done using the defined application generated ID. This ID is independent of third party change. All application objects reference the security

credential via the middle layer ID. This provides the ability to detect changes, add alias records, and not disturb the application.

The method's algorithm creates a new alias table for users. The record in the table contains an alias name, which is the old name. The column...