# US 2003/0070069 A1 · Authentication module for an enterprise access management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0070069 A1
- Document ID: US20030070069A1
- Status: Published application
- Kind: A1
- Application number: 09/976,666
- Filed: 2001-10-10
- Published: 2003-04-10
- Earliest claimed: 2001-10-10
- Inventors: Abhijit Belapurkar; Gayathri Krishnamurthy; Maneesh Bhandari
- Web page: https://patentgrep.com/patent/US20030070069A1

## CPC

- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A pluggable authentication module (PAM) is designed for compatibility with a receiver component. In response to a request for a protected web resource, the receiver component receives a user identification (user ID) from a secure and trusted source; the receiver component need not receive a password corresponding to the user ID. The receiver component generates and sends a login request to the PAM for authentication of the user. The login request contains a representation of the user ID, but is void of a corresponding user password. The receiver component and the PAM perform a trust establishment protocol that enables the PAM to determine whether the login request (and the received user ID) is legitimate.

## Claims

### Claim 1

A user authentication method comprising:
obtaining a user identification (ID) recognizable by an enterprise access management (EAM) system;
generating a login request based upon said user ID, said login request being void of a user password corresponding to said user ID; and
evaluating said login request with a processing module compatible with said EAM system.

### Claim 2 (depends on 1)

A method according to claim 1, wherein said evaluating step comprises determining whether said login request was generated by a trusted source.

### Claim 3 (depends on 1)

A method according to claim 1, wherein said evaluating step comprises validating said user ID.

### Claim 4 (depends on 3)

A method according to claim 3, further comprising said EAM system performing an access management action if said validating step validates said user ID.

### Claim 5 (depends on 1)

A method according to claim 1, wherein said user ID represents a user authenticated by a system independent of said EAM system.

### Claim 6

A user authentication method comprising:
obtaining a user identification (ID) recognizable by an enterprise access management (EAM) system;
creating an encrypted expression based upon said user ID; and
sending said encrypted expression to a processing module compatible with said EAM system.

### Claim 7 (depends on 6)

A method according to claim 6, further comprising generating a login request that includes said encrypted expression.

### Claim 8 (depends on 7)

A method according to claim 7, wherein said encrypted expression is sent to said processing module with said login request.

### Claim 9 (depends on 7)

A method according to claim 7, wherein said login request is void of a user password corresponding to said user ID.

### Claim 10 (depends on 6)

A method according to claim 6, wherein said creating step encrypts a hash to create said encrypted expression.

### Claim 11 (depends on 10)

A method according to claim 10, further comprising performing a hashing operation on a string to compute said hash, wherein said string is based upon said user ID.

### Claim 12

A user authentication method comprising:
receiving a login request at a processing module compatible with an enterprise access management (EAM) system, said login request including a user identification (ID) recognizable by said EAM system, and said login request being void of a user password corresponding to said user ID; and
said processing module evaluating said login request to determine whether said login request was generated by a trusted source.

### Claim 13 (depends on 12)

A method according to claim 12, further comprising generating a parameter based upon user ID.

### Claim 14 (depends on 13)

A method according to claim 13, further comprising performing a hashing operation on said parameter to compute a hash.

### Claim 15 (depends on 14)

A method according to claim 14, further comprising:
encrypting said hash to create a first encrypted expression;
extracting a second encrypted expression from said parameter; and
comparing said first encrypted expression to said second encrypted expression.

### Claim 16 (depends on 15)

A method according to claim 15, further comprising validating said login request if said comparing step results in a match between said first encrypted expression and said second encrypted expression.

### Claim 17 (depends on 16)

A method according to claim 16, further comprising said EAM system performing an access management action if said validating step validates said login request.

### Claim 18 (depends on 14)

A method according to claim 14, further comprising:
extracting an encrypted expression from said parameter;
decrypting said encrypted expression to obtain a second hash; and
comparing said hash to said second hash.

### Claim 19 (depends on 18)

A method according to claim 18, further comprising validating said login request if said comparing step results in a match between said hash and said second hash.

### Claim 20 (depends on 19)

A method according to claim 19, further comprising said EAM system performing an access management action if said validating step validates said user ID.

### Claim 21

A user authentication method comprising:
obtaining a user identification (ID) recognizable by an enterprise access management (EAM) system;
forming a string based upon said user ID and an identifier;
performing a hashing operation on said string to compute a hash;
encrypting said hash, with an encryption algorithm that utilizes a key corresponding to said identifier, to create an encrypted expression; and
generating a login request that includes said user ID and a parameter derived from said encrypted expression, said login request being void of a user password corresponding to said user ID.

### Claim 22 (depends on 21)

A method according to claim 21, wherein said encrypting step utilizes a symmetric encryption algorithm.

### Claim 23 (depends on 21)

A method according to claim 21, wherein said string is formed as a concatenation of said user ID and said identifier.

### Claim 24 (depends on 21)

A method according to claim 21, further comprising receiving said login request at a processing module compatible with said EAM system.

### Claim 25 (depends on 24)

A method according to claim 24, further comprising said processing module:
generating said string from parameters included with said login request; and
performing said hashing operation on said string to compute a second hash.

### Claim 26 (depends on 25)

A method according to claim 25, further comprising said processing module:
extracting said identifier from said login request;
retrieving a stored key corresponding to said identifier; and
encrypting said second hash, with an encryption algorithm that utilizes said stored key, to create a second encrypted expression.

### Claim 27 (depends on 26)

A method according to claim 26, further comprising said processing module:
extracting said encrypted expression from said login request;
comparing said encrypted expression to said second encrypted expression; and
validating said login request if said comparing step results in a match between said first encrypted expression and said second encrypted expression.

### Claim 28 (depends on 25)

A method according to claim 25, further comprising said processing module:
extracting said identifier and said encrypted expression from said login request;
retrieving a stored key corresponding to said identifier; and
decrypting said encrypted expression, with a decryption algorithm that utilizes said stored key, to obtain a decrypted expression.

### Claim 29 (depends on 28)

A method according to claim 28, further comprising said processing module:
comparing said second hash to said decrypted expression; and
validating said login request if said comparing step results in a match between said second hash and said decrypted expression.

### Claim 30

A computer program embodied on a computer-readable medium, said computer program having computer-executable instructions for carrying out a method comprising:
obtaining a user identification (ID) recognizable by an enterprise access management (EAM) system;
creating an encrypted expression based upon said user ID; and
sending said encrypted expression to a processing module compatible with said EAM system.

### Claim 31

A computer program embodied on a computer-readable medium, said computer program having computer-executable instructions for carrying out a method at a processing module compatible with an enterprise access management (EAM) system, said method comprising:
receiving a login request including a user identification (ID) recognizable by said EAM system, said login request being void of a user password corresponding to said user ID; and
evaluating said login request to determine whether said login request was generated by a trusted source.
