Endpoint privacy preservation with cloud conferencing

Abstract

In one embodiment, a first request may be received from a first endpoint to access a cloud-based conference platform. The first request can include a first access token. Based at least on the first request, a first certificate may be provided to the first endpoint, wherein the first certificate may not include an identity of the first endpoint. A second request may be received from a second endpoint to access the cloud-based conference platform. The second request can include a second access token. Based at least on the second request, a second certificate can be provided to the second endpoint, wherein the second certificate may not include an identity of the second endpoint. Data can be routed within the cloud-based conference platform between the first endpoint and second endpoint based at least upon the first certificate and the second certificate.

Description

TECHNICAL FIELD

The present technology pertains to computer-based networking, and more specifically to privacy preservation in a cloud-based networking environment.

BACKGROUND

As more enterprises and private consumers shift toward cloud-based networking for communication and data manipulation, challenges arise due to an increasing amount of bad parties seeking to access, without authorization, information stored in cloud-based networks. Such information may include sensitive data being shared such as work-related documents or the names of the parties communicating with each other and the organizations/enterprises that the parties belong to. Parties communicating via a cloud-based network may not want unauthorized parties to know their identities due to privacy concerns. This may be due to the fact that inferences can be made if an unauthorized party is aware of the identities of parties in communication with each other via a cloud-based network. Such inferences may be reinforced when data regarding the amount and duration of communications between the parties is known in addition to the identities of the parties.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited features and other advantages of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example cloud architecture including nodes and devices interconnected by various methods of communication;

FIG. 2 illustrates an example cloud service management system;

FIG. 3 illustrates an example network environment 300 which may utilize decentralized key distribution;

FIG. 4 illustrates an example network environment 400 which may utilize centralized key distribution;

FIG. 5 illustrates an example embodiment of token generation;

FIG. 6 illustrates an example procedure utilizing a decentralized key distribution;

FIG. 7 illustrates an example procedure utilizing a centralized key distribution;

FIG. 8 illustrates an example architecture of some embodiments of the present technology;

A component or a feature that is common to more than one drawing is indicated with the same reference number in each of the drawings.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.

Overview

In some embodiments, a first request may be received from a first endpoint to access a cloud-based conference platform. The first request can include a first access token that does not include an identity of the first endpoint. A second request may be received from a second endpoint to access the cloud-based conference platform. The second request can include a second access token that does not include an identity of the second endpoint. Data can be routed within the cloud-based conference platform between the first endpoint and second endpoint based at least upon the first certificate and the second certificate. These and other features are disclosed in greater detail below.

Description

Some embodiments of the present technology can hide the identities of endpoints (for example, call participants) in a conference call using the cloud conference server while still allowing endpoints to exchange media (for example, voice/data/video) through the media distribution device (MDD) provided by the cloud conference service. The participating endpoints can also be made aware of the identities of the other participating endpoints on the conference call. This may be accomplished, in some embodiments, by utilizing an authorization server to act as an intermediary to determine whether endpoints/call participants of an intended conference call conducted via a cloud conference server are authorized to participate in the conference call. The authorization server may provide keys (for instance, encrypted keys) to the endpoints for verification that the endpoints may access the conference call. In some embodiments, the authorization server can be the Enterprise identity provider (IdP) to generate a certificate/token for an endpoint which is trying to establish its identity (may be referred to as an authenticating party or authenticating endpoint) to access to the cloud conference server, wherein the certificate may conceal the identity of the endpoint call participant. The authenticating party/authenticating endpoint may also inform the identity provider about the identities of other participants in the conference call authorized to receive the identity of the authenticating party.

Assertion verification can be a process by which a relying party can verify that an assertion of a user's ownership of a certain credential/certificate is valid. In some embodiments, an IdP can provide a short-term certificate (e.g., single use) such that an ownership assertion needs to be changed for each request (e.g., each call) to access a cloud conferencing server so that the cloud conferencing server cannot identify that the same endpoint is making multiple calls.

Endpoints may use a third party authorization service (for example, OAuth 2.0) to gain access to a cloud conferencing server. In some embodiments, an Enterprise identity provider can perform the role of authorization server and the cloud conferencing server can perform the role of resource server. Endpoints may authenticate with the authorization server/Enterprise identity provider in order to receive an access token from the authorization server/Enterprise identity provider. The endpoints can then utilize the access token to receive authorization to access the cloud conferencing server and MDD. Thus, some embodiments provide that the endpoints do not make their true identities known to the cloud conferencing server.

In some embodiments, an IdP proxy can mask the true identities of authenticating parties/endpoints during identity assertion generation, which may be exchanged using an offer/answer process. The IdP proxy can be implemented with a script (e.g., JavaScript®) that runs in an isolated security context within a network and communicates via a secure message passing channel. Identity assertion generation may be followed by identity assertion validation/verification, which can be performed by the IdP proxy. In some embodiments, the identity assertion generated by the IdP proxy may not include the true identity of the authenticating party. Participants of the conference call can receive the true identity of the authenticating party, but identity assertion validation/verification performed by the MDD may not receive the true identity of the authenticating party since the MDD may not be authorized by the authenticating party to receive the true identity.

In some embodiments, a web browser may instantiate an IdP proxy. This may allow the IdP to load any script necessary into the IdP proxy. The resulting code may run in the IdP's security context. The IdP can register an object with the browser that conforms to a corresponding application program interface (API). The web browser may invoke methods on the object registered by the IdP proxy to generate or verify/validate identity assertions.

Endpoint identities or true identities may refer to the identities of each individual participant and/or the identities of the organizations associated with the endpoints/call participants. Some embodiments of the present technology may hide the identities of the individual call participants/endpoints from the cloud conferencing server while some embodiments may hide both the identities of the individual call participants and the identities of the organizations associated with the call participants. This would, among other things, improve privacy among call participants because outside parties would not be able to make inferences based on tracked call sessions made in the cloud conference server.

For instance, a call session facilitated by a cloud conferencing server could be targeted to gain information which would be valuable to businesses competing with the participants of a call session. If the true identities of the call session participants are discovered by an unauthorized third party, the unauthorized third party could use the information to make inferences regarding the nature of the call session. For example, an unauthorized third party could infer that the endpoint parties of the call session are conducting business deals or negotiations. This information could be valuable to an unauthorized third party as it may allow the unauthorized third party to gain an unfair business advantage over its competitors by having information that was intended to be confidential. Thus, privacy concerns may dictate a need for concealment of endpoint identities in a cloud conferencing server environment.

In some embodiments, a decentralized key distribution method can include a first conference call participant (for example, a speaker in the conference call) who establishes a secure connection with other conference call participants. The conference call participants can authenticate individually with an authentication server in order to receive a certificate/token for access to the conference call hosted by a cloud conference server. The initiating participant may request from the authentication server an encrypted key/token/group identifier for distribution to the group of conference call participants in order to exchange media. In some embodiments, the cloud conference server cannot access the encrypted media exchanged between participants and does not know the identity of the participants, but can modify the Real-time Transport Protocol (RTP) header.

In some embodiments, a centralized key distribution method can include an on-premise Enterprise Key Management Server (KMS), which may act as an intermediary/proxy authorization server. Endpoint participants of a conference call can authenticate with the KMS, and the initiating endpoint participant may request a group identifier/encryption key from the KMS in order for the conference call participants to communicate with each other while utilizing the cloud conference server. The KMS may provide the identities of conference call participants to other conference call participants authorized to receive the information.

In some embodiments, the present technology can be utilized in a cloud computing environment. For example, an exemplary cloud or virtual computing environment is provided in FIG. 1. FIG. 1 illustrates an example cloud architecture 100 including nodes and devices interconnected by various methods of communication. Cloud 150 can be a public, private, and/or hybrid cloud system which may include one or more public and private cloud networks in communication with each other. Cloud 150 can include resources, such as a cloud conferencing server 152; MDD 154; one or more Firewalls 197; Load Balancers 193; WAN optimization platforms 195; devices 187, such as switches, routers, intrusion detection systems, Auto VPN systems, or any hardware or software network device; one or more servers 180, such as a primary use network server, a data backup server, dynamic host configuration protocol (DHCP), domain naming system (DNS), or storage servers; virtual machines (VMs) 190; controllers, such as a communications controller 200 or a management device.

MDD 154 can forward media flows transmitted by conference call participants to other conference call participants, and may sometimes forward only a subset of flows based on voice activity detection or other criteria. In some embodiments, a switching MDD 154 may make limited modifications to RTP [RFC3550] headers, for example, but the actual media content (e.g., voice or video data) can be unaltered. An advantage of switched conferencing is that MDD 154 can be deployed on general-purpose computing hardware. This, in turn, means that it is possible to deploy a switching MDD 154 in virtualized environments, including private and public clouds.

Cloud resources can be physical, software, virtual, or any combination thereof. For example, a cloud resource can include a server running one or more VMs or storing one or more databases. Moreover, cloud resources can be provisioned based on requests (e.g., client or tenant requests), schedules, triggers, events, signals, messages, alerts, agreements, necessity, or any other factor. For example, cloud 150 can provision network recovery services, application services, software development services, database services, storage services, management services, monitoring services, configuration services, administration services, backup services, disaster recovery services, bandwidth or performance services, intrusion detection services, VPN services, or any type of services to any device, server, network, client, or tenant.

In addition, cloud 150 can handle traffic and/or provision services. For example, cloud 150 can provide network routing/re-routing services, network data backup services, configuration services, such as auto VPN, automated deployments, automated wireless configurations, automated policy implementations, and the like. In some embodiments, the cloud 150 can collect data about a client or network and generate configuration settings for specific service, device, or networking deployments. For example, the cloud 150 can generate security policies, subnetting and routing schemes, forwarding schemes, NAT settings, VPN settings, and/or any other type of configurations. The cloud 150 can then push or transmit the necessary data and settings to specific devices or components to manage a specific implementation or deployment. For example, the cloud 150 can generate VPN settings, such as IP mappings, port number, and security information, and send the VPN settings to specific, relevant device(s) or component(s) identified by the cloud 150 or otherwise designated. The relevant device(s) or component(s) can then use the VPN settings to establish a VPN tunnel according to the settings. As another example, the cloud 150 can generate and manage network diagnostic tools or graphical user interfaces.

Furthermore, cloud 150 can provide specific services for clients—namely, client A 110, client B 120, and client C 130. For example, cloud 150 can deploy a network or specific network components, configure links or devices, automate services or functions, or provide any other services for the clients. Other non-limiting example services performable by cloud 150 can include network administration services, network monitoring services, content filtering services, application control, WAN optimization, firewall services, gateway services, storage services, protocol configuration services, wireless deployment services, and so forth.

To this end, the clients can connect with cloud 150 through networks 160, 162, and 164, respectively. More specifically, client A 110, client B 120, and client C 130 can each connect with cloud 150 through networks 160, 162, and 164, respectively, in order to access resources from cloud 150, communicate with cloud 150, or receive any services from cloud 150. Networks 160, 162, and 164 can each refer to a public network, such as the Internet; a private network, such as a LAN; a combination of networks; or any other network, such as a VPN or an overlay network.

Moreover, the clients can each include one or more networks. For example, client A 110, client B 120, and client C 130 can each include one or more LANs and VLANs. In some cases, a client can represent one branch network, such as a LAN, or multiple branch networks, such as multiple remote networks. For example, client A 110 can represent a single LAN network or branch, or multiple branches or networks, such as a branch building or office network in Los Angeles and another branch building or office network in New York. If a client includes multiple branches or networks, the multiple branches or networks can each have a designated connection to the cloud 150. For example, each branch or network can maintain a tunnel to the cloud 150. Alternatively, all branches or networks for a specific client can connect to the cloud 150 via one or more specific branches or networks. For example, traffic for the different branches or networks of a client can be routed through one or more specific branches or networks. Further, client A 110, client B 120, and client C 130 can each include one or more routers, switches, appliances, client devices, VMs, or any other devices.

Each client can also maintain links between branches. For example, client A can have two branches, and the branches can maintain a link between each other. Thus, in some cases, branches can maintain a tunnel between each other, such as a VPN tunnel. Moreover, the link or tunnel between branches can be generated and/or maintained by the cloud 150. For example, the cloud 150 can collect network and address settings for each branch and use those settings to establish a tunnel between branches. In some cases, the branches can use a respective tunnel between the respective branch and the cloud 150 to establish the tunnel between branches. For example, branch 1 can communicate with cloud 150 through a tunnel between branch 1 and cloud 150 to obtain the settings for establishing a tunnel between branch 1 and branch 2. Branch 2 can similarly communicate with cloud 150 through a tunnel between branch 2 and cloud 150 to obtain the settings for the tunnel between branch 1 and branch 2.

In some cases, cloud 150 can maintain information about each client network, in order to provide or support specific services for each client, such as network traffic monitoring, network traffic routing/re-routing, security, or VPN services. Cloud 150 can also maintain one or more links or tunnels to the clients. For example, cloud 150 can maintain a VPN tunnel to one or more devices in client A's network. In some cases, cloud 150 can configure the VPN tunnel for a client, maintain the VPN tunnel, or automatically update or establish any link or tunnel to the client or any devices of the client.

The cloud 150 can also monitor device and network health and status information for client A 110, client B 120, and client C 130. To this end, client A 110, client B 120, and client C 130 can synchronize information with cloud 150. Cloud 150 can also manage and deploy services for the clients. For example, cloud 150 can collect network information about client A 110 and generate network and device settings to automatically deploy a service for client A 110. In addition, cloud 150 can update device, network, and service settings for the clients.

Those skilled in the art will understand that the cloud architecture 150 can include any number of nodes, devices, links, networks, or components. In fact, embodiments with different numbers and/or types of clients, networks, nodes, cloud components, servers, software components, devices, virtual or physical resources, configurations, topologies, services, appliances, deployments, or network devices are also contemplated herein. Further, cloud 150 can include any number or types of resources, which can be accessed and utilized by clients or tenants. The illustration and examples provided herein are intended for clarification of some embodiments of the present technology.

Moreover, as far as communications, packets (e.g., traffic and/or messages) can be exchanged among the various nodes and networks in the cloud architecture 100 using specific network protocols. In particular, packets can be exchanged using wired protocols, wireless protocols, security protocols, OSI-Layer specific protocols, or any other protocols. Some non-limiting examples of protocols can include Session Initiation Protocol (SIP), protocols from the Internet Protocol Suite, such as TCP/IP; OSI (Open Systems Interconnection) protocols, such as L1-L7 protocols; routing protocols, such as RIP, IGP, BGP, STP, ARP, OSPF, EIGRP, NAT; or any other protocols or standards, such as HTTP, SSH, SSL, RTP, FTP, SMTP, POP, PPP, NNTP, IMAP, Telnet, SSL, SFTP, WIFI, Bluetooth, VTP, ISL, IEEE 802 standards, L2TP, IPSec, etc. In addition, various hardware and software components or devices can be implemented to facilitate communications both within a network and between networks. The various hardware and software components or devices can also be referred to as nodes and some examples are switches, hubs, routers, access points (APs), antennas, network interface cards (NICs), modules, cables, firewalls, servers, repeaters, sensors, and the like.

FIG. 2 illustrates a schematic block diagram of an example communications controller 200. Communications controller 200 can serve as a cloud service management system for cloud 150. In particular, communications controller 200 can manage cloud operations, client communications, service provisioning, network configuration and monitoring, and the like. For example, communications controller 200 can manage cloud service provisioning, such as cloud storage, media, streaming, security, or administration services. In some embodiments, communications controller 200 can manage VMs; networks, such as client networks or software-defined networks (SDNs); service provisioning; and the like.

Communications controller 200 can include several subcomponents, including hardware and software components such as a scheduling function 204, a processor 205, a dashboard process 206, data 208, a networking function 210, a management layer 212, and a communication interface 202. The various subcomponents can be implemented as hardware and/or software components (e.g., processor 205, memory, data structures, etc.). Moreover, although FIG. 2 illustrates one example configuration of the various components of communications controller 200, those of skill in the art will understand that the components can be configured in a number of different ways and can include any other type and number of components. For example, networking function 210 and management layer 212 can belong to one software module or multiple separate modules. Other modules can be combined or further divided up into more subcomponents.

Scheduling function 204 can manage scheduling of procedures, events, or communications. For example, scheduling function 204 can schedule when resources should be allocated from cloud 150. As another example, scheduling function 204 can schedule when specific instructions or commands should be transmitted to the network (e.g., one or more client devices). In some cases, scheduling function 204 can provide scheduling for operations performed or executed by the various subcomponents of communications controller 200. Scheduling function 204 can also schedule resource slots, virtual machines, bandwidth, device activity, status changes, nodes, updates, and the like.

Dashboard process 206 can provide an interface or front end where clients can access, consume, and generally monitor cloud services. For example, dashboard process 206 can provide a web-based frontend where clients can configure client devices or networks that are cloud-managed, provide client preferences, specify policies, enter data, upload statistics, configure interactions or operations, etc. In some cases, dashboard process 206 can provide visibility information, such as views of client networks or devices, and even provide diagnostic information, discussed in greater detail below—e.g., dashboard process 206 can provide a view of the status or conditions of the client's network, the operations taking place, services, performance, a topology or layout, specific network devices, protocols implemented, running processes, errors, notifications, alerts, network structure, ongoing communications, data analysis, etc.

In some cases, dashboard process 206 can provide a graphical user interface (GUI) for the client to monitor the client network, the devices, statistics, errors, notifications, etc., and even make modifications or setting changes through the GUI. The GUI can depict charts, lists, tables, tiles, network trees, maps, topologies, symbols, structures, or any graphical object or element. In addition, the GUI can use color, font, shapes, or any other characteristics to depict scores, alerts, or conditions. In some cases, dashboard process 206 can also handle user or client requests. For example, the client can enter a service request through dashboard process 206.

Data 208 can include any data or information, such as management data, statistics, settings, preferences, profile data, logs, notifications, attributes, configuration parameters, client information, network information, and the like. For example, communications controller 200 can collect network statistics from the client and store the statistics as part of data 208. In some cases, data 208 can include performance and/or configuration information. This way, communications controller 200 can use data 208 to perform management or service operations for the client. Data 208 can be stored on a storage or memory device on communications controller 200, a separate storage device connected to communications controller 200, or a remote storage device in communication with communications controller 200.

Networking function 210 can perform networking calculations, such as network addressing, or networking service or operations, such as auto VPN configuration or traffic routing/re-routing. For example, networking function 210 can perform filtering functions, switching functions, failover functions, high availability functions, network or device deployment functions, resource allocation functions, messaging functions, traffic analysis functions, port configuration functions, mapping functions, packet manipulation functions, path calculation functions, loop detection, cost calculation, error detection, or otherwise manipulate data or networking devices. In some embodiments, networking function 210 can handle networking requests from other networks or devices and establish links between devices. In some embodiments, networking function 210 can perform queueing, messaging, or protocol operations.

Management layer 212 can include logic to perform management operations. For example, management layer 212 can include the logic to allow the various components of communications controller 200 to interface and work together. Management layer 212 can also include the logic, functions, software, and procedure to allow communications controller 200 to perform monitoring, management, control, and administration operations of other devices, cloud 150, the client, applications in cloud 150, services provided to the client, or any other component or procedure. Management layer 212 can include the logic to operate communications controller 200 and perform particular services configured on communications controller 200.

Moreover, management layer 212 can initiate, enable, or launch other instances in communications controller 200 and/or cloud 150. In some embodiments management layer 212 can also provide authentication and security services for cloud 150, the client, controller 200, and/or any other device or component. Further, management layer 212 can manage nodes, resources, VMs, settings, policies, protocols, communications, and the like. In some embodiments, management layer 212 and networking function 210 can be part of the same module. However, in some embodiments, management layer 212 and networking function 210 can be separate layers and/or modules.

Communications interface 202 allows communications controller 200 to communicate with the client, as well as any other device or network. Communications interface 202 can be a network interface card (NIC), and can include wired and/or wireless capabilities. Communications interface 202 allows communications controller 200 to send and receive data from other devices and networks. In some embodiments, communications controller 200 can include multiple communications interfaces for redundancy or failover. For example, communications controller 200 can include dual NICs for connection redundancy.

FIG. 3 illustrates an example network environment 300 which may utilize decentralized key distribution to increase privacy of endpoints (e.g., callers) in a conference call. The network environment 300 can include one or more networks, such as networks 304A and 304B. In some embodiments, endpoint callers may originate their communications from either network 304A or network 304B, using cloud based network 302 with cloud server 360 to communicate in a cloud-based environment. Networks 304A and 304B can include one or more local area networks (LANs), virtual LANs, wireless networks, physical network segments, logical network segments, underlay networks, overlay networks, etc. Each of the networks 304A and 304B can also include one or more physical and/or logical network segments. For example, networks 304A and 304B can be segmented into VLANs in order to separate traffic within the networks 304A and 304B. Moreover, networks 304A and 304B can be interconnected by network 302. Network 302 can include a cloud-based computing network, server 360, private network, such as a LAN, and/or a public network such as the Internet.

Networks 304A and 304B can include various devices 314, 316, 320, 322, 326, 328, 330, 338, 342, 346, 348, 350, 352, such as servers and client devices, interconnected via network devices 306-310, 312, 332-336, and 344, such as routers, firewalls, switches, and so forth. In some embodiments, networks 304A and 304B can be cloud-based networks themselves and may include clusters of nodes. Further, networks 304A and 304B and/or one or more nodes in networks 304A and 304B can be configured to provision network or application services, such as firewall services, content filtering services, application security services, web security services, bandwidth services, VPN services, web services, database services, remote access services, Internet services, and so forth.

Network 370 can be a cloud-based network with server 372. In some embodiments, server 372 may serve the role of identity provider for endpoints/callers that desire an authorization token to communicate with other endpoints/callers in a communication between the parties such as for communication in a conference call facilitated in cloud network 302 by cloud server 360.

In some embodiments, client device (endpoint) 314 of network 304A may desire communication with client device (endpoint) 352 of network 304B via cloud network 302. It is noted that endpoints 314 and 352 are shown as laptops, but may be represented by smartphones, desktop computers, tablets, and the like. Endpoint 314 and endpoint 352 may desire that their communications via network 302 be private in that their identities are not detectable by third parties operating in cloud network 302. Endpoints 314 and 352 may gain access to cloud conferencing server 360 by utilizing, for example, OAuth 2.0. Prior to communicating with each other via the MDD in the cloud conferencing server 360, both endpoints 314 and 352 may be authenticated with authorization server 372. Authorization server 372 can provide endpoints 314 and 352 with authorization tokens/certificates to access cloud conferencing server and MDD 360.

The tokens/certificates utilized by endpoints 314 and 352 for access to cloud conferencing server 360 may not list the identities of endpoints 314 and 352 such that a third party gaining unauthorized access to the tokens would not be able to determine the identities of endpoints 314 and 352. In some embodiments, the individual identities associated with endpoints 314 and 352 can be concealed in the tokens. The tokens/certificates can be obtained by endpoints 314 and 352 by communicating with the identity provider 372. In some embodiments, identity provider 372 may provide endpoints 314 and 352 with a short-term token/certificate, or a one-time use token. An authenticating party, for instance endpoint 314 or endpoint 352, can request that identity provider 372 generate a token/certificate that does not include the identity of the authenticating party. In some embodiments, short-term certificates and identity assertions can be changed for an endpoint for each call of a plurality of conference calls so that the cloud conferencing server cannot determine that the same endpoint is making multiple calls.

After endpoints 314 and 352 receive their authenticated tokens/certificates, each endpoint may attempt to access cloud network 302 by providing their authenticated tokens/certificates. In some embodiments, cloud server 360 and identity provider 372 may be in communication such that identity provider 372 provides cloud server 360 with a listing of tokens assigned to endpoints/callers that are authorized to access cloud network 302. Thus, in some embodiments, when endpoints 314 and 352 receive their authenticated tokens and short-term certificates, they may communicate with each other in cloud network 302 without cloud server 360 having access to their respective identities because cloud server 360 may only have information regarding authorized tokens and not the identities behind the authorized tokens/certificates. This can increase privacy among the communicating endpoints by preventing unauthorized parties from learning identifying information about the communicating endpoints. Further, this may prevent unauthorized parties from making inferences regarding the nature of the communications between the endpoint callers 314 and 352.

In some embodiments, identity provider 372 may create an identity assertion/token/certificate that disguises or omits the identity of the authenticated endpoint/caller. Thus, upon requesting access to cloud network 302 by, for example, an offer/answer procedure with cloud conferencing server 360, the authenticated endpoint/caller can provide an authenticated token from identity provider 372 that does not contain identifying information of the authenticated endpoint/caller. In some embodiments, upon requesting a token/certificate to enter a conference call hosted by cloud conferencing server 360, an authenticating endpoint/caller may provide identity provider 372 with information regarding the identities of other endpoints/callers that plan to join the conference call in cloud 302. The authenticating endpoint/caller may also provide identity provider 372 with a listing of other endpoints/callers authorized to receive the identity of the authenticating party. This can allow callers in cloud network 302 to confirm that the parties they are communicating with in cloud network 302 are the intended parties. In some embodiments, this can be achieved while withholding the identities of the communicating parties.

This may be accomplished by utilizing a decentralized key distribution procedure. In a decentralized key distribution system, an endpoint/caller may convey IP addresses and port numbers in an offer/answer procedure for communicating, for example, group keys with other callers in cloud network 302. This may provide for group key management by providing to the conference call participants associated group identifiers/keys.

In a decentralized key distribution system, an initiating endpoint/caller may test connectivity with remote peers (e.g., other endpoints/callers) by using, for example, Interactive Connectivity Establishment (ICE). The initiating endpoint may establish a secure connection with the remote peers/remote endpoints/remote callers, and the remote callers can mutually authenticate using, for example, short-term certificates provided by identity provider 372. This can be done by a relying party (e.g., a remote peer/caller desiring to join a conference call) validating their remote peer's certificate and assertion. The relying party can request identity provider 372 to provide the identity of an authenticated party (i.e., a remote peer on the same conference call). If the relying party is authorized to receive the identity of the authenticated party, the identity provider 372 may provide the identity of the authenticated party to the relying party. Identity provider 372 may determine parties authorized to receive identifying endpoint information by utilizing a list of authorized parties provided to it from the authenticating party.

The initiating endpoint/caller can generate a group identifier/group symmetric key (e.g., a group end-to-end encryption key) for encrypting and decrypting media exchanged between endpoints in a conference call hosted by cloud server 360. The initiating endpoint (e.g., a speaker of the conference call) can distribute the group symmetric key and encryption algorithm (e.g., Authenticated Encryption with Associated Data (AEAD) to the other participants/callers/endpoints in the conference call using a secure communication channel. In some embodiments, participants in the conference call can also establish a Datagram Transport Layer Security-Real-time Transport Protocol (DTLS-SRTP) session with cloud conferencing server 360 to generate a hop-by-hop key. The participants in the conference call may use a group end-to-end key to encrypt media transmitted in cloud network 302 to other participants in the conference call. The conference call participants may use the hop-by-hop key to encrypt RTP Control Protocol (RTCP) communications and calculate message integrity for Real-time Transport Protocol (RTP) headers. Thus, in some embodiments, cloud conferencing server 360 may not have access to encrypted real-time media in cloud 302 that is communicated between endpoints 314 and 352, but cloud conferencing server 360 may modify the RTP header associated with an encrypted communication.

The devices, nodes, and networks described in network environment 300 are non-limiting examples of devices, nodes, and networks provided for clarification purposes. One of ordinary skill in the art will readily recognize that network environment 300 can include more or less devices, nodes, and networks than those depicted in FIG. 3. Moreover, one of ordinary skill in the art will readily recognize that network environment 300 can include other configurations, architectures, topologies, and so forth. Indeed, other configurations, architectures, topologies, systems, and implementations are contemplated herein.

FIG. 4 illustrates an example network environment 400 which may utilize centralized key distribution to increase privacy of endpoints (e.g., callers) in a conference call. The network environment 400 can include one or more networks, such as networks 304A and 304B. In some embodiments, endpoint callers may originate their communications from either network 304A or network 304B, using cloud based network 302 with cloud server 360 to communicate in a cloud-based environment. Networks 304A and 304B can include one or more local area networks (LANs), virtual LANs, wireless networks, physical network segments, logical network segments, underlay networks, overlay networks, etc. Each of the networks 304A and 304B can also include one or more physical and/or logical network segments. For example, networks 304A and 304B can be segmented into VLANs in order to separate traffic within the networks 304A and 304B. Moreover, networks 304A and 304B can be interconnected by network 302. Network 302 can include a cloud-based computing network, server 360, private network, such as a LAN, and/or a public network such as the Internet.

Networks 304A and 304B can include various devices 314, 316, 320, 326, 328, 330, 338, 342, 346, 348, 350, 352, such as servers and client devices, interconnected via network devices 306-310, 312, 332-336, and 344, such as routers, firewalls, switches, and so forth. In some embodiments, networks 304A and 304B can be cloud-based networks themselves and may include clusters of nodes. Further, networks 304A and 304B and/or one or more nodes in networks 304A and 304B can be configured to provision network or application services, such as firewall services, content filtering services, application security services, web security services, bandwidth services, VPN services, web services, database services, remote access services, Internet services, and so forth.

In some embodiments, server 320 may serve the role of identity provider and key management server (KMS) for endpoints/callers that desire an authorization token to communicate with other endpoints/callers in a communication between the parties such as for communication in a conference call facilitated in cloud network 302 by cloud conferencing server 360. KMS 320 can be an on-premise enterprise KMS that may securely create, share, rotate, and store group end-to-end encryption keys for securing media communicated between endpoints/callers in a conference call facilitated by cloud conferencing server 360 in cloud network 302. In some embodiments, endpoints in a conference call may communicate with KMS 320 directly or through cloud conference server 360. Thus, cloud conference server 360 may act as a transparent proxy that does not receive application layer (L7) data exchanged between endpoints/callers and KMS 320. Endpoints may authenticate with KMS 320 by using a token/certificate provided by the identity provider and identity assertion. The endpoint initiating a media request via cloud conference server 360 can request KMS 320 to generate a group encryption key and can negotiate an encryption algorithm. KMS 320 may also provide the identities of conference call participants that are authorized to receive the group keying material. Moreover, KMS 320 may use a push or pull model to provide the group keying material to the conference call participants.

In some embodiments that utilize centralized key distribution, client device (endpoint) 314 of network 304A may desire communication with client device (endpoint) 352 of network 304B via cloud network 302. It is noted that endpoints 314 and 352 are shown as laptops, but may be represented by smartphones, desktop computers, tablets, and the like. Endpoint 314 and endpoint 352 may desire that their communications via network 302 be private in that their identities are not detectable by third parties operating in cloud network 302. Endpoints 314 and 352 may gain access to cloud conferencing server 360 by utilizing, for example, OAuth 2.0. Prior to communicating with each other in via cloud conferencing server 360, both endpoints 314 and 352 may be authenticated with identity provider/KMS 320. Identity provider/KMS 320 can provide endpoints 314 and 352 with authorization tokens/certificates to access cloud conferencing server 360.

The tokens/certificates utilized by endpoints 314 and 352 for access to cloud conferencing server 360 may not list the identities of endpoints 314 and 352 such that a third party gaining unauthorized access to the tokens would not be able to determine the identities of endpoints 314 and 352. In some embodiments, the organizations associated with endpoints 314 and 352 can be concealed in the tokens. The tokens/certificates can be obtained by endpoints 314 and 352 by communicating with identity provider/KMS 320. In some embodiments, identity provider/KMS 320 may provide endpoints 314 and 352 with a short-term token/certificate, or a one-time use token. An authenticating party, for instance endpoint 314 or endpoint 352, can request that KMS 320 generate a token/certificate that does not include the identity of the authenticating party.

After endpoints 314 and 352 receive their authenticated tokens/certificates, each endpoint may attempt to access cloud conferencing server 360 by providing their authenticated certificates. In some embodiments, cloud conferencing server 360 and identity provider/KMS 320 may be in communication such that identity provider/KMS 320 provides cloud server 360 with a listing of tokens assigned to endpoints/callers that are authorized to access cloud conferencing server 360. Thus, in some embodiments, when endpoints 314 and 352 receive their authenticated tokens, they may communicate with each other in cloud network 302 without cloud conferencing server 360 having access to their respective identities because cloud server 360 may only have information regarding authorized tokens and not the identities behind the authorized tokens/certificates. This can increase privacy among the communicating endpoints by preventing unauthorized parties from learning identifying information about the communicating endpoints. Further, this may prevent unauthorized parties from making inferences regarding the nature of the communications between the endpoint callers 314 and 352.

In some embodiments, identity provider/KMS 320 may create an identity assertion/token/certificate that disguises or omits the identity of the authenticated endpoint/caller. Thus, upon requesting access to cloud network 302 by, for example, an offer/answer procedure with cloud conferencing server 360, the authenticated endpoint/caller can provide an authenticated token from identity provider/KMS 320 that does not contain identifying information of the authenticated endpoint/caller. In some embodiments, upon requesting a token/certificate to enter a conference call hosted by cloud conferencing server 360, an authenticating endpoint/caller may provide identity provider/KMS 320 with information regarding the identities of other endpoints/callers that plan to join the conference call in cloud 302. The authenticating endpoint/caller may also provide identity provider/KMS 320 with a listing of other endpoints/callers authorized to receive the identity of the authenticating party. This can allow callers in cloud network 302 to confirm that the parties they are communicating with in cloud network 302 are the intended parties. In some embodiments, this can be achieved while withholding the identities of the communicating parties.

The devices, nodes, and networks described in network environment 400 are non-limiting examples of devices, nodes, and networks provided for clarification purposes. One of ordinary skill in the art will readily recognize that network environment 400 can include more or less devices, nodes, and networks than those depicted in FIG. 4. Moreover, one of ordinary skill in the art will readily recognize that network environment 400 can include other configurations, architectures, topologies, and so forth. Indeed, other configurations, architectures, topologies, systems, and implementations are contemplated herein.

FIG. 5 illustrates an example embodiment of token generation. A user 510 may utilize, for example, a laptop or other network computing device to receive an authenticated certificate/token that does not list the user's identification. This certificate/token may be used to access a cloud conference server (not shown) such that the user's identity is not known to the cloud conference server, but may be disclosed to other callers in the user's call conference by utilization of, for example, a group identifier. Server 512 may be an identity provider or key management server. Moreover, server 512 can function as an on-site enterprise key management server or as a remote server in a decentralized key distribution system. In FIG. 5, step 502 involves user 510 authenticating its identity with server 512. Authentication can occur through use of, for instance, a user name and password. Server 512 can generate key pairs at step 504 to send back to user 510. At step 506, a public key can be sent back to server 512. At step 508, server 512 may generate and sign the certificate/token and return the certificate/token to user 510. In some embodiments, the signed certificate/token may not include the identity of user 510 such that user 510 can utilize the signed certificate/token to access a cloud conference server without the cloud conference server knowing the identity of user 510 or the devices used by user 510 to access the cloud conference server.

FIG. 6 illustrates an example procedure 600 for endpoint privacy preservation with cloud conferencing according to one or more embodiments of the present disclosure. The steps outlined herein are exemplary and can be implemented in any combination thereof, including combinations that exclude, add, or modify steps shown in FIG. 6. At step 602, a first request can be received from a first endpoint to access a cloud-based conference platform, wherein the first request includes a first access token. Based at least on the first request, a first certificate can be provided to the first endpoint, wherein the first certificate does not include an identity of the first endpoint. If access to the cloud-based conference platform is authorized, procedure 600 may continue at step 604 wherein a second request may be received from a second endpoint to access the cloud-based conference platform, wherein the second request includes a second access token. Based at least on the second request, a second certificate can be provided to the second endpoint, wherein the second certificate does not include an identity of the second endpoint. If access to the cloud-based conference platform is authorized, procedure 600 may continue at step 606 wherein data can be routed within the cloud-based conference platform between the first endpoint and second endpoint using the MDD. Endpoints may authenticate with the MDD using, for example, a short-term certificate provided by the Enterprise IdP.

A listing of endpoints authorized to receive the identities of the other endpoints in the cloud-based conference platform that are communicating with each other may be provided to an identity provider. At step 608, a request may be received from the second endpoint for the identity of the first endpoint. If the second endpoint is authorized to receive the identity of the first endpoint (e.g., the second endpoint is one of the endpoints in the listing of endpoints authorized to receive the identity of the first endpoint), at step 610, the identity of the first endpoint can be provided to the second endpoint.

It should be noted that while certain steps within procedure 600 may be optional as described above, the steps shown in FIG. 6 are merely examples for illustration, and steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments described herein.

FIG. 7 illustrates an example procedure 700 for endpoint privacy preservation with cloud conferencing according to one or more embodiments of the present disclosure. The steps outlined herein are exemplary and can be implemented in any combination thereof, including combinations that exclude, add, or modify steps shown in FIG. 7. At step 702, a first request can be received from a first endpoint to access a cloud-based conference platform. If the first endpoint is authorized access to the cloud-based conference platform, procedure 700 can continue to step 704. In step 704, in response to the first request, a first access token can be provided to the first endpoint. Based at least on the first request, a first certificate can be provided to the first endpoint, wherein the first certificate does not include an identity of the first endpoint. Procedure 700 continues at step 706 wherein a second request may be received from a second endpoint to access the cloud-based conference platform. If the second endpoint is authorized access to the cloud-based conference platform, procedure 700 can continue to step 708. In step 708, in response to the second request, a second access token can be provided to the second endpoint and based at least on the second request, a second certificate may be provided to the second endpoint, wherein the second certificate does not include an identity of the second endpoint. The first endpoint and the second endpoint may communicate with each other in the cloud-based conference platform using at least the MDD. Endpoints can authenticate to the MDD using short-term certificates provided by the Enterprise Identity provider.

Procedure 700 may continue to step 710 wherein a listing of endpoints authorized to access the cloud-based conference platform can be received. In step 712, a request for an identity of an endpoint of the listing of endpoints authorized to access the cloud-based conference platform can be received. If the requesting endpoint is authorized to receive the requested identity, procedure 700 may continue to step 714 wherein the identity of the requested endpoint is provided to the requesting endpoint.

It should be noted that while certain steps within procedure 700 may be optional as described above, the steps shown in FIG. 7 are merely examples for illustration, and steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments described herein.

FIG. 8 illustrates an example system architecture of some embodiments of the present technology. Persons of ordinary skill in the art will also readily appreciate that other system embodiments are possible.

FIG. 8 illustrates a conventional bus computing system architecture 800 wherein the components of the system are in electrical communication with each other using a bus 805. Exemplary system 800 includes a processing unit (CPU or processor) 810 and a system bus 805 that couples various system components including the system memory 815, such as read only memory (ROM) 820 and random access memory (RAM) 825, to the processor 810. The system 800 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 810. The system 800 can copy data from the memory 815 and/or the storage device 830 to the cache 812 for quick access by the processor 810. In this way, the cache can provide a performance boost that avoids processor 810 delays while waiting for data. These and other modules can control or be configured to control the processor 810 to perform various actions. Other system memory 815 may be available for use as well. The memory 815 can include multiple different types of memory with different performance characteristics. The processor 810 can include any general purpose processor and a hardware module or software module, such as module 1832, module 2834, and module 3836 stored in storage device 830, configured to control the processor 810 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 810 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing system architecture 800, an input device 845 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 835 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 800. The communications interface 840 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 830 can be a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 825, read only memory (ROM) 820, and hybrids thereof.

The storage device 830 can include software modules 832, 834, 836 for controlling the processor 810. Other hardware or software modules are contemplated. The storage device 830 can be connected to the system bus 805. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 810, bus 805, display 835, and so forth, to carry out the function.

It can be appreciated that example system 800 can have more than one processor 810 or be part of a group or cluster of computing devices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

In some embodiments the computer-readable storage devices, media, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rack mount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. Moreover, claim language reciting “at least one of” a set indicates that one member of the set or multiple members of the set satisfy the claim. Further, features described with reference to an embodiment disclosed herein can be combined with, or implemented in, any other embodiments disclosed herein.

The techniques disclosed herein can provide increased privacy among endpoints communicating via a cloud-based network which may result in more efficient network packet processing as fewer data may be required for network packet transmissions, which may result in fewer processor cycles required to route signals and thus improved efficiency of the network processors used to implement some embodiments of the present technology.

While there have been shown and described illustrative embodiments of the present technology, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the embodiments herein. For example, the embodiments have been shown and described herein with relation to a particular communication system. However, the embodiments in their broader sense are not as limited, and may, in fact, be used with any number of communication systems.

Further, although the foregoing description has been directed to specific embodiments, it will be apparent that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that the components and/or elements described herein can be implemented as software being stored on a tangible (non-transitory) computer-readable medium, devices, and memories (e.g., disks/CDs/RAM/EEPROM/ etc.) having program instructions executing on a computer, hardware, firmware, or a combination thereof. Further, methods describing the various functions and techniques described herein can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code.

Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include cloud-based media, magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and the like. In addition, devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, tablets, wearable devices, small form factor personal computers, personal digital assistants, and the like. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example. Instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures. Accordingly this description is to be taken only by way of example and not to otherwise limit the scope of the embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the embodiments herein.

Claims

1. A non-transitory computer-readable medium including instructions stored thereon, the instructions, when executed by a processor, cause the processor to: receive a first request from a first endpoint to access a cloud-based conference platform, wherein the first request includes a first access token;based at least on the first request, provide a first certificate to the first endpoint, wherein the first certificate does not include an identity of the first endpoint;receive a second request from a second endpoint to access the cloud-based conference platform, wherein the second request includes a second access token;based at least on the second request, provide a second certificate to the second endpoint, wherein the second certificate does not include an identity of the second endpoint;route data within the cloud-based conference platform between the first endpoint and the second endpoint based at least on the first certificate and the second certificate;receive, via an identity provider, a third request for an identity of one of the first endpoint or the second endpoint, the third request sent from another one of the first endpoint or the second endpoint; andprovide, via the identity provider, the identity of the one of the first endpoint or the second endpoint unless the one of the first endpoint or the second endpoint has not authorized the identity provider to provide the identity of the one of the first endpoint or the second endpoint.

2. The non-transitory computer-readable medium of claim 1, wherein access tokens provide at least one of temporary access or one-time access to the cloud-based conference platform.

3. The non-transitory computer-readable medium of claim 1, wherein access tokens are provided by the identity provider hosted by an enterprise network associated with the first endpoint.

4. The non-transitory computer-readable medium of claim 1, wherein the identity provider provides access tokens and is hosted by a separate network from the first endpoint and the second endpoint.

5. The non-transitory computer-readable medium of claim 1, wherein, the instructions further cause the processor to receive, via the identity provider, a listing of endpoints,the listing of endpoints is sent from the first endpoint,the listing of endpoints includes all endpoints authorized to receive the identity of the first endpoint, andthe listing of endpoints includes at least the second endpoint.

6. The non-transitory computer-readable medium of claim 1, wherein, the third request is for the identity of the first endpoint,the third request is sent from the second endpoint, andthe second endpoint is included in a listing of endpoints authorized to receive the identity of the first endpoint.

7. A non-transitory computer-readable medium including instructions stored thereon, the instructions, when executed by a processor, cause the processor to: receive a first request from a first endpoint to access a cloud-based conference platform;in response to the first request, provide a first access token to the first endpoint;based at least on the first request, provide a first certificate to the first endpoint, wherein the first certificate does not include an identity of the first endpoint;receive a second request from a second endpoint to access the cloud-based conference platform;in response to the second request, provide a second access token to the second endpoint;based at least on the second request, provide a second certificate to the second endpoint;receive a third request from the second endpoint for the identity of the first endpoint; andin response to the third request, provide the identity of the first endpoint based at least upon a listing of endpoints authorized to access the cloud-based conference platform and to receive identifying information,wherein, the second certificate does not include an identity of the second endpoint, andthe first endpoint and the second endpoint communicate with each other in the cloud-based conference platform using at least the first certificate and the second certificate.

8. The non-transitory computer-readable medium of claim 7, wherein the instructions further cause the processor to receive the listing of endpoints,the listing of endpoints is sent from the first endpoint,the listing of endpoints includes all endpoints authorized to receive the identity of the first endpoint, andthe listing of endpoints includes the second endpoint.

9. The non-transitory computer-readable medium of claim 7, wherein, the third request is for the identity of the first endpoint,the third request is sent from the second endpoint, andthe second endpoint is included in the listing of endpoints.

10. The non-transitory computer-readable medium of claim 7, wherein access tokens provide at least one of temporary access or one-time access to the cloud-based conference platform.

11. The non-transitory computer-readable medium of claim 7, wherein access tokens are provided by an identity provider hosted by an enterprise network associated with the first endpoint.

12. The non-transitory computer-readable medium of claim 7, wherein access tokens are provided by an identity provider hosted by a separate network from the first endpoint and the second endpoint.

13. A system comprising: one or more processors;an identity provider; anda memory configured to store a process, the process, when executed by the one or more processors, causes the one or more processors to: receive a first request from a first endpoint of a first network to access a cloud-based conference platform in a cloud network, wherein the first request includes a first access token;based at least on the first request, provide a first certificate to the first endpoint, wherein the first certificate does not include an identity of the first endpoint;receive a second request from a second endpoint of a second network to access the cloud-based conference platform in the cloud network, wherein the second request includes a second access token;based at least on the second request, provide a second certificate to the second endpoint, wherein the second certificate does not include an identity of the second endpoint;route data within the cloud-based conference platform of the cloud network between the first endpoint and the second endpoint based at least on the first certificate and the second certificate;receive, via the identity provider proxy, a third request for an identity of one of the first endpoint or the second endpoint, the third request sent from another one of the first endpoint or the second endpoint; andprovide, via the identity provider, the identity of the one of the first endpoint or the second endpoint unless the one of the first endpoint or the second endpoint has not authorized the identity provider to provide the identity of the one of the first endpoint or the second endpoint.

14. The system of claim 13, wherein access tokens provide at least one of temporary access or one-time access to the cloud-based conference platform of the cloud network.

15. The system of claim 13, wherein the identity provider provides access tokens and is hosted by a third network.

16. The system of claim 13, wherein, the process further causes the one or more processors to receive, via the identity provider, a listing of endpoints,the listing of endpoints is sent from the first endpoint,the listing of endpoints includes all endpoints authorized to receive the identity of the first endpoint, andthe listing of endpoints includes at least the second endpoint.

17. The system of claim 13, wherein, the third request is for the identity of the first endpoint,the third request is sent from the second endpoint, andthe second endpoint is included in a listing of endpoints authorized to receive the identity of the first endpoint.

18. A method comprising: receiving a first request from a first endpoint to access a cloud-based conference platform, wherein the first request includes a first access token;based at least on the first request, providing a first certificate to the first endpoint, wherein the first certificate does not include an identity of the first endpoint;receiving a second request from a second endpoint to access the cloud-based conference platform, wherein the second request includes a second access token;based at least on the second request, providing a second certificate to the second endpoint, wherein the second certificate does not include an identity of the second endpoint;routing data within the cloud-based conference platform between the first endpoint and the second endpoint based at least on the first certificate and the second certificate,receiving, via an identity provider, a third request for an identity of one of the first endpoint or the second endpoint, the third request sent from another one of the first endpoint or the second endpoint; andproviding, via the identity provider, the identity of the one of the first endpoint or the second endpoint unless the one of the first endpoint or the second endpoint has not authorized the identity provider to provide the identity of the one of the first endpoint or the second endpoint.

19. The method of claim 18, wherein access tokens are provided by the identity provider hosted by an enterprise network associated with the first endpoint.

20. The method of claim 18, wherein the identity provider provides access tokens and is hosted by a separate network from the first endpoint and the second endpoint.