Method and Apparatus for Multi-Domain Identity Interoperability and certification

• US 20090089625A1
• Filed: 08/04/2008
• Published: 04/02/2009
• Est. Priority Date: 08/02/2007
• Status: Active Grant

• Current Assignee: FuGen Solutions, Inc. (8K Miles Software Services Ltd.)
• Original Assignee: FuGen Solutions, Inc. (8K Miles Software Services Ltd.)
• Inventors: Simha, Vijay S., Kannappan, Lakshmanan, Prafullchandra, Hemma
• Granted Patent: US 8,434,129 B2
• Time in Patent Office: Days
• US Class Current: 714/39
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations

Abstract

A method and apparatus to provide identity management deployment interoperability and compliance verification. 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

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.

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

3. 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.

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

5. 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.

6. 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.

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

and

generating a validation report.