Techniques for identity-enabled interface deployment

• US 9,183,374 B2
• Filed: 07/13/2011
• Issued: 11/10/2015
• Est. Priority Date: 07/15/2010
• Status: Expired due to Fees

• Current Assignee: Micro Focus Software, Inc. (Open Text Corporation)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Earl, Douglas Garry, Carter, Stephen R
• Primary Examiner(s): Shepperd, Eric W
• Application Number:
  US13/182,090
• Publication Number:
  US 20120017085A1
• Time in Patent Office: 1,581 Days
• Field of Search: 726/7, 726/19, 726/21, 726/22, 726 1- 5, 726 9- 10, 726/12, 726 26- 29, 713/150, 713155-159, 713168-169, 713172-173, 713/182, 713/185, 709201-202, 709204-205, 709/218, 709/223, 709/225, 709/229, 709/249
• US Class Current: 1/1
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807

Abstract

Techniques for providing identity-enabled interfaces for deployment are presented. Specifically, an agent of an enterprise infrastructure authenticates and acquires an agent identity for interacting with a cloud processing environment. Once the agent is deployed in the cloud processing environment, enterprise policy can be enforced within the cloud processing environment on actions occurring within the cloud. The agent acts as an Application Programming Interface between the enterprise and the cloud processing environment. The reverse is also achievable, where a cloud deploys an agent to the enterprise to deploy a cloud interface within the enterprise for policy enforcement.

Claims

1. A method implemented in a non-transitory machine-readable storage medium and processed by one or more processors configured to perform the method, comprising:

configuring a cloud agent for deployment within a target cloud environment, the cloud agent configured within an enterprise environment and the cloud agent is configured to process on processors of the target cloud environment and to use interfaces that the target cloud environment uses;

authenticating the cloud agent and obtaining a cloud agent identity;

assigning an expiration condition to the cloud agent identity that when satisfied renders the cloud agent identity invalid and providing the configured cloud agent with a mechanism to extend the expiration condition of the agent by obtaining other credentials to extend beyond the expiration condition by extending an expiration specification, wherein the agent uses the mechanism for raising a particular event that results in the agent obtaining the other credentials;

requesting, by the cloud agent, a security token from a security manager of the target cloud environment, the security token unique to the target cloud environment;

receiving, by the cloud agent, a token expiration condition with the security token, and when the token expiration condition is met, the security token becomes invalid for use within the target cloud environment; and

deploying the cloud agent to the target cloud environment for enforcement of enterprise policy within the target cloud environment, via the cloud agent.

2. The method of claim 1 further comprising, using, by the cloud agent, the security token with each request issued within the target cloud environment to validate each request and to enforce the enterprise policy with each request.

3. The method of claim 1, wherein receiving a token expiration condition further includes identifying the token expiration condition as being different from the expiration condition of the cloud agent identity.

4. The method of claim 1 further comprising, recognizing, by the cloud agent, the security token as a globally unique identifier for the target cloud environment.

5. The method of claim 1 further comprising, using, by the cloud agent a cloud provider interface dictated by the target cloud environment to interact with the security manager.

6. The method of claim 1, wherein authenticating further includes interacting with an identity service and supplying credentials for the cloud agent, the credentials supplied by an administrator via an agent console.

7. The method of claim 1, wherein assigning further includes assigning the expiration condition as a time-to-live attribute to the cloud agent identity.

8. The method of claim 1, wherein deploying further includes using, by the cloud agent, the cloud agent identity to authenticate to the target cloud environment and to enforce the enterprise policy within the target cloud environment.