Abstract: A proxy server may receive from a user endpoint, a secure connection request to a second server. The secure connection request may be matched to a globally unique identifier registered for the user endpoint by employing a device-specified identifier associated with the globally unique identifier. The proxy server may respond. with an acknowledgement to the user endpoint. The proxy server may intercept, from the user endpoint, a first secure handshake with the second server. The proxy server may initiate a second secure handshake with the second server based on the intercepted first secure handshake. The proxy server may intercept from the second server a second secure handshake response comprising a server certificate with metadata. The proxy server may generate a second certificate using the metadata and signed by a first certificate authority associated with the globally unique identifier registered for the user endpoint.

Abstract: A proxy server may receive from a user endpoint, a secure connection request to a second server. The secure connection request may comprise a globally unique identifier registered for the endpoint. The proxy server may intercept, from the user endpoint, a first secure handshake with the second server. The proxy server may initiate a second secure handshake with the second server based on the intercepted first secure handshake. The proxy server may intercept from the second server a second secure handshake response comprising a server certificate with metadata. The proxy server may generate a second certificate using the metadata and signed with a first certificate authority associated with the globally unique identifier registered for the endpoint. The proxy server may transmit to the user endpoint a modified response to the secure connection request secured with the second certificate to establish a proxied secure connection.

Abstract: A Mobile Enterprise Platform utilizes a web based service that synchronizes enterprise data between a plurality of disparate mobile devices and a plurality of backend enterprise resources. The Mobile Enterprise Platform creates a web service synchronization source instance using Hypertext Transfer Protocol (“HTTP”) for each application or database present on a plurality of mobile devices. Corresponding to each of these web service synchronization source instances is a web based synchronization service associated with a specific backend enterprise resource. Each synchronization service is web based and can thus live anywhere on the network or on a dedicated services tie as they need only to supply a small set of operations to offer synchronization capability to a variety of mobile devices.

Abstract: A Mobile Enterprise Platform utilizes a web based service that synchronizes enterprise data between a plurality of disparate mobile devices and a plurality of backend enterprise resources. The Mobile Enterprise Platform creates a web service synchronization source instance using Hypertext Transfer Protocol (“HTTP”) for each application or database present on a plurality of mobile devices. Corresponding to each of these web service synchronization source instances is a web based synchronization service associated with a specific backend enterprise resource. Each synchronization service is web based and can thus live anywhere on the network or on a dedicated services tie as they need only to supply a small set of operations to offer synchronization capability to a variety of mobile devices.