# US 2013/0254882 A1 · Multi-domain identity interoperability and compliance verification

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

- Number: US 2013/0254882 A1
- Document ID: US20130254882A1
- Status: Published application
- Kind: A1
- Application number: 13/873,165
- Filed: 2013-04-29
- Published: 2013-09-26
- Earliest claimed: 2007-08-02
- Inventors: Lakshmanan Kannappan; Vijay S. Simha; Hemma Prafullchandra
- Web page: https://patentgrep.com/patent/US20130254882A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06Q 10/10: Office automation; Time management
- G06Q 30/06: Buying, selling or leasing transactions
- H04L 63/0815: {providing single-sign-on or federations}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An identity management deployment, interoperability, and compliance verification is discussed. In one embodiment, the system also provides on-demand services including automated certification, monitoring, alerting, routing, and translation of tokens for federated identity related interactions between multi-domain identity management systems is provided.

## Claims

### Claim 1

A method of providing identity federation deployment comprising:
utilizing a pre-generated schema for generating a deployment system including interoperability between two or more SP/IDPs;
providing a testing environment to validate that the two or more SP/IDPs are capable of interoperation at the deployment level; and
creating a customized quality assurance environment to implement at least one of the SP and IDP, the customized quality assurance environment used to test deployment validation scenarios.

### Claim 2 (depends on 1)

The method of claim 1, wherein the SP is a client, and the SP is designed to interface with one or more IDPs.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
rolling out the quality assurance environment to a pre-production environment, the pre-production environment interfacing a SP/IDP with a pre-deployment version of an SP/IDP.

### Claim 4 (depends on 3)

The method of claim 3, wherein the pre-deployment version of the SP/IDP is a service provider client.

### Claim 5 (depends on 3)

The method of claim 3, further comprising:
rolling out a production environment in which a fully deployed version of an SP interface with a fully deployed version of the IDP; and
providing a tap to monitor communications between the SP and the IDP.

### Claim 6 (depends on 5)

The method of claim 5, wherein monitoring communications between the SP and the IDP comprises:
decrypting, parsing, and assembling an identity-related communication between the SP and the IDP; and
validating the identity-related communication.

### Claim 7 (depends on 6)

The method of claim 6, wherein validating the identity-related communication comprises comparing the communication to a deployment profile; and
generating a validation report.
