Novell, Inc.

Emc Corporation

Micro Focus Software Inc.

Ancestry.com Operations Inc.

Douglas Garry Earl

Lloyd Leon Burch

Stephen R Carter

Prakash Umasankar Mukkara

Nadeem Ahmad Nazeer

Kelly Ervin Sonderegger

Russell T Young

John Michael Robertson

Daniel T Ferguson

Arn D Perkins

DeeAnne Barker Higley

Douglas R Phillips

Farrell Lynn Brough

Joseph Andrew Mellmer

Jeffrey Neil Sabin

Michael C McDonald

Robert Michael Sheridan

Carolyn Bennion McClain

Robert Skousen Stilmar

Jonathan Paul Bultmeyer

Robert Mark Ward

Jason Allen Sabin

Jeremy Ray Brown

Baha Masoud

Donald B Curtis

Cameron Craig Morris

Tammy Anita Green

Rey Furner

Bryce Damon Ririe

Matt Rasmussen

Kaleb Benjamin White

Anne Gillespie Mitchell

Cory R Newey

A computing server may receive genealogical records that include historical records of deceased individuals. The computing server may normalize the genealogical records into normalized genealogical records. Normalizing the genealogical records may include converting a text string of a genealogical record into a standardized format. The computing server may stitch the normalized genealogical records into a plurality of clusters. Each cluster corresponds to an individual and includes one or more genealogical records associated with the individual. The computing server may identify a life-event record that is commonly associated with a subset of clusters, the life-event record indicating that a plurality of deceased individuals are connected through a non-familial relationship in a life event documented by the life-event record. The computing server may cause a graphical user interface to display a representation of a historical network among the plurality of deceased individuals that are connected through the non-familial relationship.

Determining relationships of historical data records

Techniques for sharing virtual machine (VM) resources are provided. A relative location for a resource within a VM is created; the relative location dynamically resolves to a particular physical location when a principal requests access to the resource at runtime. The principal is located outside an environment associated with the VM. Authentication and access restrictions are dynamically enforced against the requests made by the principal before a connection is permitted between the principal and the resource (the resource located within the environment of the VM).

Techniques for sharing virtual machine (VM) resources

Techniques for virtual Representational State Transfer (REST) interfaces are provided. A proxy is interposed between a client and a REST service over a network. The proxy performs independent authentication of the client and provides credentials to the client and for the client to authenticate to the REST service using a REST service authentication mechanism. The proxy inspects requests and responses and translates the requests and responses into formats expected by the client and the REST service. Moreover, the proxy enforces policy and audits the requests and responses occurring between the client and the REST service over the network.

Techniques for virtual representational state transfer (REST) interfaces

Techniques for secure access management to virtual environments are provided. A user authenticates to a portal for purposes of establishing a virtual machine (VM). The portal interacts with a cloud server and an identity server to authenticate the user, to acquire an Internet Protocol (IP) address and port number for the VM, and to obtain a secure token. The user then interacts with a secure socket layer virtual private network (SSL VPN) server to establish a SSL VPN session with the VM. The SSL VPN server also authenticates the token through the identity server and acquires dynamic policies to enforce during the SSL VPN session between the user and the VM (the VM managed by the cloud server).

Techniques for secure access management in virtual environments

Techniques for controlling authentication are provided. An enterprise injects a control and/or audit manager into the enterprise environment to control and in some instances audit third-party authentication services. A user attempts to access a resource that uses a third-party authentication service. The attempt is intercepted and third-party authentication handled by the manager. After authentication, a session between the user and the resource is established during which auditing services may be enacted. The user authenticates to the enterprise environment and the manager provides authentication for the user to the resource via the third-party authentication service.

Techniques for controlling authentication

Techniques for workload federated timeout are presented. A federated service manages communications between service components of a system. Each component queries the federated service to determine a last activity time by the other components of the system before timing out during a session. Each component can update its last activity time based on the discovered last activity time of one of the components to prevent a premature time out from the session.

Federated timeout

Apparatus, systems, and methods may operate to receive, at a generating identity provider (IDP), original user credentials sufficient to authenticate a user directly from a user machine, or indirectly from an initial identity provider. Additional activities may include generating, by the generating IDP, generated user credentials having the lifetime of a login session associated with the user, the lifetime initiated approximately when the original user credentials or a token associated with the user are/is validated at the generating IDP. Still further activities may include receiving a request associated with the user during the login session to access an application protected by an agent, and transmitting at least part of the generated user credentials from the generating IDP to the application to authenticate the user to the generating IDP while the login session is not terminated or expired. Additional apparatus, systems, and methods are disclosed.

Multiple access authentication

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.

Techniques for identity-enabled interface deployment

A basic architecture for managing digital identity information in a network such as the World Wide Web is provided. A user of the architecture can organize his or her information into one or more profiles which reflect the nature of different relationships between the user and other entities, and grant or deny each entity access to a given profile. Various enhancements which may be provided through the architecture are also described, including tools for filtering email, controlling access to user web pages, locating other users and making one's own location known, browsing or mailing anonymously, filling in web forms automatically with information already provided once by hand, logging in automatically, securely logging in to multiple sites with a single password and doing so from any machine on the network, and other enhancements.

Managing digital identity information

Techniques for non-repudiation of storage in cloud or shared storage environments are provided. A unique signature is generated within a cloud or shared storage environment for each file of the storage tenant that accesses the cloud or shared storage environment. Each signature is stored as part of the file system and every time a file is accessed that signature is verified. When a file is updated, the signature is updated as well to reflect the file update.

Techniques for non repudiation of storage in cloud or shared storage environments

Apparatus, systems, and methods may operate to authenticate a desktop client to an identity service (IS), to receive a request, from an application, at the IS via the desktop client for a virtual service internet protocol (IP) address associated with a service. The IS may operate to build a routing token that includes an original physical IP address associated with the service when a policy associated with the IS permits access to the service by a user identity associated with the desktop client. After the routing token is validated, the application may be connected to the service via the desktop client. The application may comprise an e-mail application or a remote control application, such as a virtual network computing (VNC) application. Additional apparatus, systems, and methods are disclosed.

Dynamic service access

Growing community of inventors

Orem, UT, United States of America

Douglas Garry Earl