Abstract: Techniques to provide proxies for web services are described. A technique may include providing proxies for web services that translate one format to a format native used, or understood, by the web service without having to rewrite existing APIs. In one embodiment, for example, an apparatus may comprise a processing unit and a network interface coupled to the processing unit. The apparatus may further include a web service executing web service requests on the processing unit using a native format. The apparatus may further include a proxy to receive a web service request in a first format via the network interface and to translate the web service request from the first format to the native format. Other embodiments are described and claimed.

Abstract: Techniques to provide proxies for web services are described. A technique may include providing proxies for web services that translate one format to a format native used, or understood, by the web service without having to rewrite existing APIs. In one embodiment, for example, an apparatus may comprise a processing unit and a network interface coupled to the processing unit. The apparatus may further include a web service executing web service requests on the processing unit using a native format. The apparatus may further include a proxy to receive a web service request in a first format via the network interface and to translate the web service request from the first format to the native format. Other embodiments are described and claimed.

Abstract: The present invention extends to methods, systems, and computer program products for separating authorization identity from policy enforcement identity. Embodiments of the invention extend the consumption phase for protected information. Two identities, an authorization identity and a policy enforcement identity, are used for acquiring, issuing and enforcing usage license instead of one identity certificate. The authorization identity is used to evaluate against usage policy. The authorization identity is similar to identification information in an identity certificate. The policy enforcement identity is used to ensure the confidentiality of granted permissions and content key. The policy enforcement identity enforces a usage license on an authorization principal's (e.g., recipient's) machine. The policy enforcement identity's enforcement of a usage license is similar use of a cryptographic key in an identity certificate.

Abstract: Business to business secure mail may be provided. Consistent with embodiments of the invention, a protected message may be received. The recipient may request a token from a trust broker, submit the token to an authorization server associated with the sender, receive a user license from the authorization server; and decrypt the protected message using the user license. The protected message may restrict actions that may be taken by the recipient, such as forwarding to other users.

Abstract: The present invention extends to methods, systems, and computer program products for separating authorization identity from policy enforcement identity. Embodiments of the invention extend the consumption phase for protected information. Two identities, an authorization identity and a policy enforcement identity, are used for acquiring, issuing and enforcing usage license instead of one identity certificate. The authorization identity is used to evaluate against usage policy. The authorization identity is similar to identification information in an identity certificate. The policy enforcement identity is used to ensure the confidentiality of granted permissions and content key. The policy enforcement identity enforces a usage license on an authorization principal's (e.g., recipient's) machine. The policy enforcement identity's enforcement of a usage license is similar use of a cryptographic key in an identity certificate.

Abstract: Business to business secure mail may be provided. Consistent with embodiments of the invention, a protected message may be received. The recipient may request a token from a trust broker, submit the token to an authorization server associated with the sender, receive a user license from the authorization server; and decrypt the protected message using the user license. The protected message may restrict actions that may be taken by the recipient, such as forwarding to other users.