Abstract:
Authorizing a requesting entity to have a server perform a particular action in a manner that is at least partially independent of the underlying target data structure. An authorization station maintains a number of role templates (310) that each define basic access permissions with respect to a number of command methods. The authorization station also maintains a number of role definitions (350) that each define access permissions for specific requesting entities by using one or more of the role templates (310). When the authorization station receives a request from the requesting entity, the authorization station then identifies the appropriate role definition (350). Using this role definition (350), the authorization station determines access permissions for the requesting entity with respect to the requested action.
Abstract:
Use of a biometric identification device in a client computer system to subsequently access an authentication system includes receiving biometric sample data which is digitally signed and combining the data with a user ID and PIN. This package of data is then securely transmitted to a biometric matching server to validate the user and the biometric sample. Once validated, the biometric matching server return the data package plus a temporary certificate and a public/private key pair to the client computer. The client computer may then use this information to access an authentication system to subsequently gain access to a secure resource.
Abstract:
A model for accessing data in an identity-centric manner. An identity (310) maybe a user, a group of users, or an organization.Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services (511 through 518) accessible by many applications (320). The data is stored in accordance with a schema that is recognized by a number of different applications and hte data service (511 through 518). When a user is to perform an operatio on the identity's (310 data, the corresponding application (320) generates a message (531) that has a structure that is recognized by the data service (511 through 518). The message (531) represents a request to perform an operation on the data structure corresponding to the identity (310). The data service (511 through 518) receives and itnerprets the message. If authorized, the data service (511 through 518) then performs the operation.
Abstract:
The present invention extends to methods, systems, and computer program products for licensing protected content to application sets. Embodiments of the invention permit a local machine to increase its participation in authorizing access to protected content. For example, an operating system within an appropriate computing environment is permitted to determine if an application is authorized to access protected content. Thus, the application is relieved from having to store a publishing license. Further, authorization decisions are partially distributed, easing the resource burden on a protection server. Accordingly, embodiments of the invention can facilitate more robust and efficient authorization decisions when access to protected content is requested.
Abstract:
Abstracting access control policy from access check mechanisms allows for richer expression of policy, using a declarative model with semantics, than what is permitted by the access check mechanisms. Further, abstracting access control policy allows for uniform expression of policy across multiple access check mechanisms. Proof-like reasons for any access query are provided, such as who has access to what resource, built from the policy statements themselves, independent of the access check mechanism that provide access. Access is audited and policy-based reasons for access are provided based on the access control policy.
Abstract:
Aspects of the subject matter described herein relate to providing file access in a multi-protocol environment. In aspects, a file server is operable to receive requests formatted according to two or more file access protocols. If a request is formatted according to a first file access protocol, the file server applies access rights associated with the file to an account associated with a requestor to determine whether to grant access. If the request is formatted according to the second file access protocol, the file server may first attempt to find an account for the requestor. If an account is not found, the file server may then grant access based on access rights associated with the file as applied to information in the request without consulting an account on the file server.
Abstract:
Access control as it relates to policies or permissions is provided based on a created model. A security policy is abstracted and can be independent of a mechanism used to protect resources. An asbstract model of a potential user, user role and/or resource is created without associating a specific individual and/or resource with a model. These abstract user models and abstract resource models can be used across applications or within disparate applications. The abstracted security policies can be selectively applied to the model. Specific users and/or resources can be associated with one or more abstract user model or abstract resource model. The models can be nested to provide configurations for larger systems.
Abstract:
Directly operating on data structures in a generic manner regardless of the type of data structure being operated upon and without requiring dedicated executable code for manipulating data structures of the particular data type. A common set of commands (e.g -. insert, delete, replace, update, query) are recognized that may be used to operate on data structures (210, 220, 230, 240) of a number of different data types. A navigation module (250) accesses a request to execute one of the common command methods on at least an identified portion of an identified data structure (210, 220, 230, 240). Then, the navigation module (250) accesses a navigation assistance module (260) to access a set of rules associated with the particular data type, the set of rules allowing the navigation module (250) to find the portion of the data structure (210, 220, 230, 240) that is to be operated on. If appropriate, the command operation is then executed on the identified portion of the data structure (210, 220, 230, 240).
Abstract:
A hint containing user mapping information is provided in messages that may be exchanged during authentication handshakes. For example, a client may provide user mapping information to the server during authentication. The hint (e.g., in the form of a TLS extension mechanism) may be used to send the domain/user name information of a client to aid the server in mapping the user's certificate to an account. The extension mechanism provides integrity and authenticity of the mapping data sent by the client. The user provides a hint as to where to find the right account or domain controller (which points to, or otherwise maintains, the correct account). Based on the hint and other information in the certificate, the user is mapped to an account. The hint may be provided by the user when he logs in. Thus, a certificate is mapped to an identity to authenticate the user. A hint is sent along with the certificate information to perform the binding. Existing protocols may be extended to communicate the additional mapping information (the hint) to perform the binding. A vendor specific extension to Kerberos is defined to obtain the authorization data based on an X.509 certificate and the mapping user name hint.
Abstract:
A messaging data structure (700) for accessing data in an identity-centric manner, An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by number of different applications and the data service. The messaging data structure (700) includes fields that identify the target data object to be operated upon using an identity field (701), a schema field (703), and an instance identifier field (704). In addition, the desired operation (707) is specified. Thus, the target data objet is operated on in an identity-centric manner.