US 8,196,191 B2Grant
Coordinating credentials across disparate credential stores
Issue Date:2012-06-05
•25 Claims
•5 Drawing Sheets
Abstract
Apparatus and methods are described for coordinating user credentials across multiple disparate credential stores. A synchronizing engine requests and receives past and present credential information from the disparate credential stores. Users indicate which, if any, of the credential information they desire to synch together. Upon common formatting of the credential information, comparisons reveal whether differences exist between the past and present versions. If differences exist, the information is updated. In this manner, users link together various passwords, keys or other secrets to maintain convenience from a single point of control, such as in a single-sign-on (SSO) environment, regardless of the disparateness of the stores. The reverse is also possible such that linked credentials are accessible from the multiple stores. Retrofitting existing SSO services is another feature as are computer program products and computing network interaction. User or enterprise policies are also used in governing these credentials.
Metadata
Inventors
- James M. Norman
- Cameron Mashayekhi
- Karl E. Ford
Application Information
Application Number:US 11/893,780
Filing Date:2007-08-17
Priority Date:2007-08-17
Art Unit:2432
Classifications
IPC:
H04L29/06
Patent Drawings (5 sheets)
Description
Field of the Invention
[0001] Generally, the present invention relates to computing environments involving heterogeneous credential stores with disparate credential information. Particularly, it relates to coordinating the disparateness of the stores into harmonized versions to provide management from a single point of control. In this manner, users can link together various passwords, keys or other secrets to maintain convenience in environments, such as single-sign-on (SSO) environments, regardless of the disparateness of the stores. Various features relate to computer program products, systems for same and methods. User or enterprise policies useful in governing these credentials and computing interaction, to name a few, are other noteworthy features.
Background of the Invention
[0002] Newer computer operating systems such as Linux, Windows XP, or Windows Vista provide multiple credential stores for network client applications' usage. These credential stores usually are utilized to provide mechanisms for applications to store credentials for the user, and retrieve them later to provide a single-sign-on (SSO) experience. More famous of these credential stores by name are: Firefox password manager, Gnome Keyring, KDE Wallet, Windows Passport, CASA, SecretStore etc.
[0003] Applications, based on their needs or at the time of their development, are closely integrated with a particular credential store. This is due to applications utilizing different credential stores and different types. As a result, there is a need for a single point of administration and access for the user. Currently, however, users must launch different management utilities for each store to manage their credentials. There are presently no tools available to provide the ability to copy, move, or “link” credentials among different versions of the same applications or multiple applications sharing the same credential. To allow credentials to be available for use and management in different stores, currently you have to manually create, copy, or delete them from one store to another. Intuitively, this is inconvenient and impractical.
[0004] Also, it presently exists that each credential store has proprietary interests in only offering solutions focused on their store and not interoperability with other stores, thereby avoiding ease of use for end users.
[0005] In view of these various problems, there is need in the art of credential stores to provide a mechanism to synchronize the values of credentials between stores, thereby eliminating the need for manually maintaining credentials in multiple stores. In that many computing configurations already have existing SSO technology, it is further desirable to leverage existing configurations by way of retrofit technology, thereby avoiding the costs of providing wholly new products. Taking advantage of existing frameworks, such as the CASA (Common Authentication Service Adapter), software offering by Novell, Inc., the common assignee of this invention, is another feature that optimizes existing resources. Any improvements along such lines should further contemplate good engineering practices, such as automation, relative inexpensiveness, stability, ease of implementation, low complexity, flexibility, etc.
Summary of the Invention
[0006] The foregoing and other problems become solved by applying the principles and teachings associated with the hereinafter-described coordinating credentials across disparate credential stores. At a high level, methods and apparatus are provided that allow linking of credentials amongst different stores and provides access to them through a utility that provides for a single point of access and management. As an important byproduct of this unique linking feature, the reverse is possible such that linked credentials are accessible from multiple stores while they are synchronized at all times. This is contemplated to be particularly useful when there are multiple versions of the same application such as a web based, command line, GUI, and perhaps older and newer versions that might have different methods of storing credentials in different stores. Linking will provide the ability to manage from a single point as well as synchronization of credentials regardless of credential store of origin. It also provides a mechanism to synchronize the values of credentials between stores, eliminating the need for manually maintaining credentials in multiple stores by the user. The user simply changes one value in a given credential and all linked or synchronized values will be updated automatically. In addition, policies can be applied to expand or filter credential availability across different stores.
[0007] In more detail, a synchronizing engine requests and receives past and present credential information from the disparate credential stores. Users indicate which, if any, of the credential information they desire to synch together. Upon common formatting of the credential information, comparisons reveal whether differences exist between the past and present versions. If differences exist, the information is updated. In this manner, users link together various passwords, keys, or other secrets to maintain convenience from a single point of control, such as in a single-sign-on (SSO) environment, regardless of the disparateness of the stores. Retrofitting existing SSO services is another feature as are computer program products and computing network interaction. User or enterprise policies are used in making various determinations.
[0008] In at least one embodiment, coordinating credentials amongst disparate stores includes requesting and receiving credential information through a common interface and in a common format. Computing first and later hashes of the credential information is used to determine if changes exist. If the hashes do not match, various user credentials are updated. Users indicate the credentials for synchronizing such as by symbolically linking two or more passwords together, the passwords being associated with the disparate credential stores.
[0009] The invention achieves, among other things: linking together various passwords, keys or other secrets to provide credential management from a single point of control, such as in a single-sign-on (SSO) environment, regardless of the disparateness of the stores; proving the reverse embodiment such that linked credentials are accessible from multiple stores; retrofitting existing SSO services; and governing by way of user or enterprise policy.
[0010] In a computing system environment, the invention may be practiced with: a user interface module for indicating various credentials to be synchronized with one another (such as by way of a CASA manager); a single-sign-on service; a synchronizing engine interfacing with the single-sign-on service; and at least two credential stores having similar or dissimilar credential information. During use, the synchronizing engine receives the credential information in a common format and is configured to compare past and present versions of the credential information to ascertain whether differences exist. In the event differences exist, the synchronizing engine is configured to update the various credentials indicated by a user via the user interface module. Computing devices of the computing environment can be physical or virtual machine(s).
[0011] Computer program products are also disclosed. For instance, a product available as a download or on a computer readable medium has components to: request and receive versions of credential information for at least two multiple disparate credential stores; commonly format the versions; and receive user input indicating various user credentials desirable to be synchronized together in the event the versions of the credential information have differences. User or enterprise policies are also used in governance of the credentials.
[0012] The CASA architecture is also exploited as part of the invention to leverage existing resources.
[0013] These and other embodiments of the present invention will be set forth in the description which follows, and in part will become apparent to those of ordinary skill in the art by reference to the following description of the invention and referenced drawings or by practice of the invention. The claims, however, indicate the particularities of the invention.
Brief Description of the Drawings
[0014] The accompanying drawings incorporated in and forming a part of the specification, illustrate several aspects of the present invention, and together with the description serve to explain the principles of the invention. In the drawings:
[0015] FIG. 1 is a diagrammatic view in accordance with the present invention of a representative computing environment for coordinating credentials across disparate credential stores;
[0016] FIG. 2 is a diagrammatic view in accordance with the present invention of a more detailed representative computing environment for coordinating credentials across disparate credential stores;
[0017] FIG. 3 is a high-level flow chart in accordance with the present invention for coordinating credentials across disparate credential stores; and
[0018] FIG. 4 is a representative diagrammatic view in accordance with the present invention for establishing policy or linking credentials of disparate credential stores.
Detailed Description of the Illustrated Embodiments
[0019] In the following detailed description of the illustrated embodiments, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention and like numerals represent like details in the various figures. Also, it is to be understood that other embodiments may be utilized and that process, mechanical, electrical, arrangement, software and/or other changes may be made without departing from the scope of the present invention: In accordance with the present invention, methods and apparatus for coordinating credentials across disparate credential stores are hereinafter described.
[0020] With reference to FIG. 1 , a representative computing environment 10 for coordinating credentials occurs by way of one or more computing devices 15 or 15′ arranged as individual or networked physical or virtual machines. In a traditional sense, an exemplary computing device typifies a server 17, such as a grid or blade server. Alternatively, it includes a general or special purpose computing device in the form of a conventional fixed or mobile computer 17 having an attendant monitor 19 and user interface 21. The computer internally includes a processing unit for a resident operating system, such as DOS, WINDOWS, MACINTOSH, VISTA, UNIX, and LINUX, to name a few, a memory, and a bus that couples various internal and external units, e.g., other 23, to one another. Representative other items 23 include, but are not limited to, PDA's, cameras, scanners, printers, microphones, joy sticks, game pads, satellite dishes, hand-held devices, consumer electronics, minicomputers, computer clusters, main frame computers, a message queue, a peer machine, a broadcast antenna, a web server, an AJAX client, a grid-computing node, a peer, a virtual machine, a web service endpoint, a cellular phone, or the like. The other items may also be stand alone computing devices 15′ in the environment 10 or the computing device itself.
[0021] In either, storage devices are contemplated and may be remote or local. While the line is not well defined, local storage generally has a relatively quick access time and is used to store frequently accessed data, while remote storage has a much longer access time and is used to store data that is accessed less frequently. The capacity of remote storage is also typically an order of magnitude larger than the capacity of local storage. Regardless, storage is representatively provided for aspects of the invention contemplative of computer executable instructions, e.g., software, as part of computer program products on readable media, e.g., disk 14 for insertion in a drive of computer 17. Computer executable instructions may also be available as a download or reside in hardware, firmware or combinations in any or all of the depicted devices 15 or 15′.
[0022] When described in the context of computer program products, it is denoted that items thereof, such as modules, routines, programs, objects, components, data structures, etc., perform particular tasks or implement particular abstract data types within various structures of the computing system which cause a certain function or group of functions. In form, the computer product can be a download or any available tangible media, such as RAM, ROM, EEPROM, CD-ROM, DVD, or other optical disk storage devices, magnetic disk storage devices, floppy disks, or any other tangible medium which can be used to store the items thereof and which can be assessed in the environment.
[0023] In network, the computing devices communicate with one another via wired, wireless or combined connections 12 that are either direct 12a or indirect 12b. If direct, they typify connections within physical or network proximity (e.g., intranet). If indirect, they typify connections such as those found with the internet, satellites, radio transmissions, or the like, and are given nebulously as element 13. In this regard, other contemplated items include servers, routers, peer devices, modems, T1 lines, satellites, microwave relays or the like. The connections may also be local area networks (LAN) and/or wide area networks (WAN) that are presented by way of example and not limitation. The topology is also any of a variety, such as ring, star, bridged, cascaded, meshed, or other known or hereinafter invented arrangement.
[0024] With the foregoing representative computing environment as backdrop, FIGS. 2 and 3 show a high-level architecture and overall flow of the invention. That is, a plurality of disparate credential stores 40-1, 40-2, 40-3, 40-4, 40-5 have dissimilar credential information, such as keys, passwords, or other secrets, based primarily on the propriety nature of the store. Representatively, the stores include, but are not limited to, SecretStore, Firefox Password Manager, Gnome Keyring, KDE Wallet and miCASA, respectively. A single-sign-on service 50 in the computing environment consists of one or more existing applications that are useful to the user for enjoying SSO convenience from one or more computing devices. In that the disparateness of the stores 40 tends to complicate SSO, especially considering that credential information is updated over time, is inconsistent in form or storage from one store to the next, has little if any commonality amongst the stores, etc., the invention further includes a synchronizing engine 60 (with attendant files 62, 64) and a layer 70 intermediate the stores 40 and the synchronizing engine. During use, users indicate which, if any, of the credential information they desire to synch together and, upon common formatting of the credential information by way of the synch engine 60 and layer 70, all linked or synchronized information is updated automatically.
[0025] In more detail, Novell Inc.'s CASA brand software (Common Authentication Services Adapter) 51 is a common authentication and security package that provides a set of libraries for application and service developers to enable single sign-on for an enterprise network. Version 1.7, for example, provides a local, session-based credential store (called miCASA) that is populated with desktop and network login credentials, given generically as 40-5. A CASA manager 52 serves as user interface module, such as on monitor 19 (FIG. 1 ), whereby users can undertake the linking of credentials of the various stores 40.
[0026] Currently, CASA manager contains drivers/connectors to the credential stores 40. Upon request, each of these drivers return an enumeration of credentials through a common interface and in a common format, steps 100 and 102. (Together, this is referred to as a Common Credential Format (CCF), step 104.) In a representative embodiment, the format is an XML schema and each driver produces an XML document describing the credential information of the stores 40. So that the CASA manager 52 and the stores 40 have format commonality, the layer 70 is configured there between. Otherwise, the CASA manager interfaces with users as normal and the credential stores keep their own proprietary format.
[0027] Upon the return, one embodiment of the invention contemplates storing the credential information as a shadow file 64, step 106. A hash of the credential information occurs at this time and is likewise stored with the shadow file. The user, through the CASA Manager, can then select the various credentials they wish to link together or synchronize, step 108. In one embodiment, this is referred to as a symbolic link and is stored in the policy file 62, step 110, for use by the synchronizing engine.
[0028] Diagrammatically, FIG. 4 shows various credential stores 40-1, 40-2, . . . 40-n, returning various credential information 80, such as Password 1, Password 2, . . . Password n, to the user interface module, such as per screen shots or web pages 85 on a monitor of a computing device. In turn, the user selects which of the credentials 80 they desire to synch together. In this case, each of Password 1 and Password 2 are selected, such as by a highlighting box 87, and are linked by clicking on a dedicated linking icon button 89. Of course, those skilled in the art will recognize other techniques for linking credential information of the various stores together.
[0029] Returning to FIGS. 2 and 3 , upon reaching a criterion, such as a configured interval or based on some trigger policy, the synchronizing engine 60 updates the earlier version of credentials, step 112, by requesting and receiving a new CCF document from each driver. It computes a new hash for the latest or updated version and compares it to the hash earlier-stored in the shadow file(s). If the hashes match, the credential information remains accurate and no further updating is necessary, other than to delay for some pre-defined period, step 118, and repeat the process, e.g., steps 112, and 114. On the other hand, if the hashes do not match, changes are effectuated at step 116. In a representative embodiment, change effectuation consists of the sync engine 60 comparing the CCF documents of the current request with the shadow request. Based on policy, changes are then made either to the shadow file, the target store, or both. The sync engine also queries the symbolic link information file for linked credential keys. If needed, changes to the linked shadow files are propagated to the appropriate store.
[0030] For instance, if a user or enterprise policy requires a user to update their single-sign-on password every, 30 days, such as per 91, FIG. 4 , and the user's password for their Firefox account has not changed, the foregoing allows the inquiry to examine when and if the passwords for the SSO and Firefox are different. If different, the invention recognizes it and effectuates an invisible change to the user such that they can still enjoy a SSO experience, without needing to go back to their Firefox account and change their password, and login credentials to match their SSO password. In other words, the present invention recognizes that users often desire to keep many passwords updated together, without actually having to undertake the work necessary to keep them updated, and accomplishes the change for the individual automatically.
[0031] For example, Firefox stores a credential as a username and a password for services requiring authentication. Often, other applications using the same username and password for authentication store that information as a cn (common name) and a pin. The user will recognize that the password saved by Firefox is the same information saved as the pin by another application in a different store. This invention allows the user to link or synchronize the password saved by Firefox with the pin saved by the other application. Hence, when the password changes so does the pin.
[0032] In the alternative, however, it should be appreciated that users may want to avoid any linking whatsoever of credential information and so a mechanism, such as default condition of no-linking (absent an affirmative indication of linking) or a no-linking icon button 93, FIG. 4 , can be used in certain instances. In this manner, credentials can be kept strictly isolated if desired.
[0033] In the case of conflicts, resolution can be accomplished by the policy the user sets up while creating a link between two or more credential keys. In this regard, the policy might be to treat a particular store as Master and another as a Servant, to select a hierarchy of stores having priority over other stores, or to let the user resolve the conflict manually using an Administration or other tool. The policy may also be a time frame, a security measure, combinations thereof, or any hereinafter contemplated feature useful in defining conditions on the linking.
[0034] In any embodiment, certain advantages and benefits over the prior art should be readily apparent. For example, but not limited to, the invention provides advantage over the art according to: 1) the ability to link and synchronize credentials across multiple stores according to application(s) of policy; 2) providing an “umbrella service” giving users a single point of use, management, and administration for multiple credential stores. (Compared to the prior art, others focus on proprietary solutions, not interoperability between stores.); 3) overcoming complexity in the working environment of standard operating systems. (An illustration of this relates to current Linux distributions that, by default, provide the two popular choices of desktops (Gnome, and KDE) and each come with its own credential store and the applications that use one or the other, but not both. Now users can utilize the instant invention and use all effectively.) Appreciating complexity in computing environments, other expansions to the invention include, but are not limited to: adding peer-to-peer linking and synchronization capability for users to synchronize their multiple desktops (e.g., peer-to-peer Windows brand workstations linked to peer-to-peer Linux desktops, or vice versa); or having linking capability between clients and servers (e.g., linking desktop credential store(s) to eDirectory SecretStore); and 4) the ability to apply uniform policy across disparate stores through a single point of management.
[0035] Finally, one of ordinary skill in the art will recognize that additional embodiments are also possible without departing from the teachings of the present invention. This detailed description, and particularly the specific details of the exemplary embodiments disclosed herein, is given primarily for clarity of understanding, and no unnecessary limitations are to be implied, for modifications will become obvious to those skilled in the art upon reading this disclosure and may be made without departing from the spirit or scope of the invention. Relatively apparent modifications, of course, include combining the various features of one or more figures with the features of one or more of other figures.
Claims
The invention claimed is:
1. In a computing system environment, a method of coordinating user credentials across multiple disparate credential stores, comprising:
determining credential information for at least two of said multiple disparate credential stores;
commonly formatting said credential information for displaying to a user via a common interface, without altering a format of said credential information in the at least two said multiple disparate credential stores;
by the user, indicating via the common interface various user credentials of the commonly formatted said credential information for synchronizing;
by the user, linking via the common interface at least a portion of the various user credentials of the at least two of said multiple disparate credential stores indicated for synchronizing;
determining updated credential information for the at least two of said multiple disparate credential stores;
commonly formatting said updated credential information; and
if the updated credential information and the credential information differ, updating the various linked user credentials of the at least two of said multiple disparate credential stores with the received updated credential information.
2. The method of claim 1, further including comparing a first hash of the commonly formatted said credential information to a second hash of the commonly formatted said updated credential information when determining said differences.
3. The method of claim 2, further including storing the first hash or second hash in a shadow file.
4. The method of claim 1, wherein the indicating various user credentials for synchronizing further includes symbolically linking two or more passwords together, the passwords being associated with the at least two of said multiple disparate credential stores.
5. The method of claim 1, further including establishing a policy for when the determining updated credential information for the at least two of said multiple disparate credential stores occurs.
6. The method of claim 1, further including retrofitting an existing single-sign-on service with a synchronizing engine to manage the updating.
7. The method of claim 1, further including indicating various user credentials for no-synchronizing.
8. The method of claim 1, wherein the updating the various user credentials further includes synchronizing a first password of a first of the at least two of said multiple disparate credential stores to a second password of a second of the at least two of said multiple disparate credential stores.
9. In a computing system environment, a method of coordinating user credentials across multiple disparate credential stores, comprising:
requesting credential information for at least two of said multiple disparate credential stores;
receiving the requested credential information through a common interface and in a common format, said common format being displayed to a user via the common interface without altering a format of the requested credential information in the at least two of said multiple disparate credential stores;
computing a first hash for the received credential information;
by the user, linking via the common interface at least a portion of the received credential information for the at least two of said multiple disparate credential stores;
requesting updated credential information for the at least two of said multiple disparate credential stores;
receiving the updated credential information through the common interface and in the common format;
computing a second hash for the received updated credential information; and
if the second hash does not match the first hash, updating the various linked user credentials for the at least two of said multiple disparate credential stores with the received updated credential information.
10. The method of claim 9, wherein the requesting updated credential information occurs upon a criterion of an established policy.
11. The method of claim 9, further including providing a synchronizing engine to interface with a single-sign-on service, the synchronizing engine for the requesting and receiving the credential information and the updated credential information.
12. The method of claim 11, further including interfacing the synchronizing engine and the single-sign-on service with a layer intermediate the multiple disparate credential stores.
13. The method of claim 9, further including indicating the various user credentials to be updated.
14. The method of claim 13, wherein the indicating further includes symbolically linking two or more passwords together, the passwords being associated with the at least two of said multiple disparate credential stores.
15. A non-transitory computer program product available as a download or on a computer readable medium having executable instructions for coordinating user credentials across multiple disparate credential stores, comprising:
a first component for requesting and receiving credential information for at least two of said multiple disparate credential stores and, thereafter, updated credential information for the at least two of said multiple disparate credential stores;
a second component to commonly format the credential information and the updated credential information for the at least two of said multiple disparate credential stores, the second component performing the step of commonly formatting for display to a user without altering a format of the credential information and the updated credential information in the at least two of said multiple disparate credential stores;
a third component to receive user input indicating various user credentials of the requested and received credential information desired to be linked and to be synchronized together in the event the requested and received credential information and the updated credential information have differences; and
a fourth component for determining whether the credential information and the updated credential information actually have said differences.
16. The computer program product of claim 15, wherein one or more of the components reside with a synchronizing engine for retrofitting with an existing single-sign-on service.
17. The computer program product of claim 15, further including a fifth component for storing a policy, the fourth and fifth components in communication with one another so that the determining said differences between the credential information and the updated credential information occurs according to the policy.
18. A computing system for coordinating user credentials across multiple disparate credential stores, comprising:
a user interface module for indicating by a user various credentials to be synchronized with one another;
a single-sign-on service;
a synchronizing engine interfacing with the single-sign-on service; and
at least two credential stores of the multiple disparate credential stores having dissimilar credential information, wherein the synchronizing engine receives the dissimilar credential information in a common format without altering a format of the dissimilar credential information in the multiple disparate credential stores and is configured to link at least a portion of the dissimilar credential information from the multiple disparate credential stores and to compare past and present versions of the dissimilar credential information to ascertain whether differences exist, in the event differences exist, the synchronizing engine being configured to update the various linked credentials indicated by a user via the user interface module.
19. The computing system of claim 18, further including a variety of files accessible by the synchronizing engine to ascertain user or enterprise policies.
20. The computing system of claim 18, further including an aggregation and distribution layer intermediate the at least two credential stores and the synchronizing engine.
21. The computing system of claim 18, wherein the user interface module is a CASA manager.
22. The computing system of claim 18, wherein the at least two credential stores include one or more of a Firefox password manager, Gnome Keyring, KDE Wallet, Windows Passport, CASA store, and SecretStore.
23. The computing system of claim 18, further including a driver for retrieving the credential information from the at least two credential stores.
24. The computing system of claim 18, wherein the synchronizing engine is a non-transitory computer program product available as a download or on a computer readable medium having executable instructions for installation on one or more physical computing devices.
25. The computing system of claim 18, wherein the synchronizing engine is further configured to apply uniform policy across the at least two credential stores.
Patent Citations (65)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6006018(A) | 1999-12-01 | Burnett et al. | Applicant |
| US6067623(A) | 2000-05-01 | Blakley, III et al. | Applicant |
| US6182229(B1) | 2001-01-01 | Nielson | Applicant |
| US6615253(B1) | 2003-09-01 | Bowman-Amuah | Applicant |
| US6651168(B1) | 2003-11-01 | Kao et al. | Applicant |
| US6779117(B1) | 2004-08-01 | Wells | Applicant |
| US6779155(B1) | 2004-08-01 | Bahrs et al. | Applicant |
| US6971005(B1) | 2005-11-01 | Henry et al. | Applicant |
| US7058180(B2) | 2006-06-01 | Ferchichi et al. | Applicant |
| US7076795(B2) | 2006-07-01 | Hahn | Applicant |
| US7107310(B2) | 2006-09-01 | McCarthy | Applicant |
| US7107610(B2) | 2006-09-01 | Lortz | Applicant |
| US7137006(B1) | 2006-11-01 | Grandcolas et al. | Applicant |
| US7275259(B2) | 2007-09-01 | Jamieson et al. | Applicant |
| US7310734(B2) | 2007-12-01 | Boate et al. | Applicant |
| US7496953(B2) | 2009-02-01 | Andreev et al. | Applicant |
| US7552222(B2) | 2009-06-01 | Garimella et al. | Applicant |
| US7562113(B2) | 2009-07-01 | Labarge et al. | Applicant |
| US7634803(B2) | 2009-12-01 | Birk et al. | Applicant |
| US7644086(B2) | 2010-01-01 | Boozer et al. | Applicant |
| US7703128(B2) | 2010-04-01 | Cross et al. | Applicant |
| US7788497(B2) | 2010-08-01 | Luo et al. | Applicant |
| US2002/0046064(A1) | 2002-04-01 | Maury et al. | Examiner |
| US2003/0012382(A1) | 2003-01-01 | Ferchichi et al. | Applicant |
| US2003/0195970(A1) | 2003-10-01 | Dinh et al. | Applicant |
| US2004/0083238(A1) | 2004-04-01 | Louis et al. | Examiner |
| US2004/0260953(A1) | 2004-12-01 | Jamieson et al. | Applicant |
| US2005/0005094(A1) | 2005-01-01 | Jamieson et al. | Applicant |
| US2005/0081055(A1) | 2005-04-01 | Patrick et al. | Applicant |
| US2005/0097166(A1) | 2005-05-01 | Patrick et al. | Applicant |
| US2005/0097352(A1) | 2005-05-01 | Patrick et al. | Applicant |
| US2005/0144482(A1) | 2005-06-01 | Anuszewski | Applicant |
| US2005/0171872(A1) | 2005-08-01 | Burch et al. | Examiner |
| US2005/0268307(A1) | 2005-12-01 | Gates et al. | Examiner |
| US2005/0289341(A1) | 2005-12-01 | Ritola et al. | Applicant |
| US2005/0289644(A1) | 2005-12-01 | Wray | Applicant |
| US2006/0013393(A1) | 2006-01-01 | Ferchichi et al. | Applicant |
| US2006/0037066(A1) | 2006-02-01 | Audebert | Applicant |
| US2006/0047625(A1) | 2006-03-01 | Ho et al. | Examiner |
| US2006/0075224(A1) | 2006-04-01 | Tao | Applicant |
| US2006/0080352(A1) | 2006-04-01 | Boubez et al. | Applicant |
| US2006/0218630(A1) | 2006-09-01 | Pearson et al. | Applicant |
| US2006/0235935(A1) | 2006-10-01 | Ng | Applicant |
| US2006/0248577(A1) | 2006-11-01 | Beghian et al. | Applicant |
| US2007/0006291(A1) | 2007-01-01 | Barari et al. | Applicant |
| US2007/0143829(A1) | 2007-06-01 | Hinton et al. | Applicant |
| US2007/0157296(A1) | 2007-07-01 | Lioy | Applicant |
| US2007/0220268(A1) | 2007-09-01 | Krishnaprasad et al. | Applicant |
| US2007/0283425(A1) | 2007-12-01 | Ture et al. | Applicant |
| US2008/0016232(A1) | 2008-01-01 | Yared et al. | Applicant |
| US2008/0021997(A1) | 2008-01-01 | Hinton | Applicant |
| US2008/0059804(A1) | 2008-03-01 | Shah et al. | Applicant |
| US2008/0072320(A1) | 2008-03-01 | Hurley | Applicant |
| US2008/0077809(A1) | 2008-03-01 | Hayler et al. | Applicant |
| US2008/0092215(A1) | 2008-04-01 | Soukup et al. | Applicant |
| US2008/0104411(A1) | 2008-05-01 | Agrawal et al. | Applicant |
| US2008/0184349(A1) | 2008-07-01 | Ting | Examiner |
| US2008/0196090(A1) | 2008-08-01 | Baron et al. | Applicant |
| US2008/0263365(A1) | 2008-10-01 | Aupperle et al. | Applicant |
| US2008/0276309(A1) | 2008-11-01 | Edelman | Applicant |
| US2008/0301784(A1) | 2008-12-01 | Zhu et al. | Applicant |
| US2008/0320576(A1) | 2008-12-01 | Curling | Applicant |
| US2009/0007248(A1) | 2009-01-01 | Kovaleski | Applicant |
| US2009/0013395(A1) | 2009-01-01 | Marcus et al. | Applicant |
| US2009/0320118(A1) | 2009-12-01 | Muller et al. | Applicant |
Non-Patent Literature (20)
- Novell, Inc. “Common Authentication Service Adapter (CASA),” Novell Developer Kit, www.novell.com, Nov. 18, 2005, 55 pps.Applicant
- Bandit, “Common Authentication Service Adapter (CASA) Architecture,” www.bandit-project.org/index.php/Common—Authentication—Services—Adapter—%28CASA%29—Architecture, Jul. 19, 2007, 4 pps.Applicant
- Bandit, “Roadmap,” www.bandit-project.org/index.php/Roadmap, 6 pps.Applicant
- Bandit, “Common Authentication Service Adapter (CASA) Architecture,” www.bandit-project.org./index.php?title=Common—Authentication—Services—Adapter—%28CASA%29—Architecture&diff=3826&oldid=2955, Jul. 19, 2007, 4 pps.Applicant
- Bandit, “Common Authentication Service Adapter (CASA) Architecture,” www.bandit-project.org/index.php?title=Common—Authentication—Services—Adapter—%28CASA%29—Architecture&diff=3826&oldid=1822, Aug. 17, 2007, 5 pps.Applicant
- Bandit, “Common Authentication Service Adapter (CASA) Architecture,” /www.bandit-project.org/index.php?title=Common—Authentication—Services—Adapter—%28CASA%29—Architecture&action=history, Jul. 19, 2007, 2 pps.Applicant
- USPTO Office Action dated Oct. 13, 2010 for U.S. Appl. No. 11/897,737, 11 pgs.Applicant
- USPTO Office Action dated Dec. 22, 2010 for U.S. Appl. No. 12/036,596, 29 pgs.Applicant
- USPTO Office Action dated Dec. 14, 2010 for U.S. Appl. No. 12/023,401, 19 pgs.Applicant
- USPTO Office Action dated Mar. 17, 2011 for U.S. Appl. No. 11/897,737, 12 pgs.Applicant
- USPTO Office Action dated Feb. 22, 2011 for U.S. Appl. No. 11/901,397, 22 pgs.Applicant
- USPTO Office Action dated May 25, 2011 for U.S. Appl. No. 12/036,596.Applicant
- USPTO Office Action dated Sep. 2, 2010 for U.S. Appl. No. 11/893,780.Applicant
- USPTO Office Action dated Jan. 7, 2011 for U.S. Appl. No. 11/893,780.Applicant
- USPTO Office Action dated Feb. 22, 2011 for U.S. Appl. No. 11/901,397.Applicant
- Microsoft, “Find and Replace,” Microsoft Office Word 2003, Screenshot, printed Aug. 11, 2007 1 page.Applicant
- Free Download Center, “Find and Replace Tool for Word 1.0 screenshot,” www.freedownloancenter.com/Utilities/Misc Text Editing Tools/Find and . . . Aug. 29, 2007 1 page.Applicant
- Microsoft, “Find and Replace”, Microsoft Office Word 2003, Screenshot, printed Sep. 17, 2007, 1 page.Applicant
- Free Download Center, “Finda and Replace Tool for Word 1.0 screenshot”, www.freedownloadcenter.com/Utilities/Misc—Text—Editing—Tools/Find—and . . . , Sep. 17, 2007 1 page.Applicant
- U.S. Appl. No. 11/901,397 Sep. 17, 2010 Office Action.Applicant