Configuring a Pulse Collaboration Meeting Server

If your environment includes Pulse clients, you can set up your device as a meeting server so that your end users can start meetings from Pulse instead of having to log in to their secure gateway web interface.

Pulse clients can list more than one Pulse Collaboration server.

To set up your device as a meeting server for Pulse clients:

1.From the admin console, select Pulse > Connections.

2.Click the connection set containing the server you want to define as a meeting server.

3.Under Connections, click the connection server.

4.Under Options, select:

•Support Pulse Collaboration integration on this connection - Define this server as a meeting server and make it available in your end-user's Pulse Secure.

•Support Remote Access on this connection - Allow users to log in to this server using the web interface. If you want this server to be only a meeting server (users cannot log in to this server through the web interface), clear this option. However, make sure the Support Pulse Collaboration integration on this connection is selected.

5.Click Save Changes.

End users can start meetings when the Pulse client is not connected to a server. With this scenario, the Pulse client attempts to log in to the meeting server using saved credentials, if available. If saved credentials do not exist, or the server login fails, the end user is prompted to enter their credentials.

If the Pulse client is connected to a Pulse server when the user starts a meeting, the client first checks to see if the meeting server is the same server that Pulse is currently connected to. If they are the same server, then the meeting starts immediately. If they are different servers, the client then checks if the end user is in the same authentication group on both servers. If it is the same authentication group, the client can use the existing user session to single sign-on (SSO) into the meeting server. This SSO to a meeting server feature is configurable through the admin console.

To configure Pulse Collaboration SSO:

1.From the admin console, select Users > User Realms>.

2.Select an existing realm, or create a new Realm.

3.On the General page, select the Session Migration and Sharing check box. Additional options appear.

4.Choose one of the following options:

•Enable Session Migration - Copy the user session from the currently connected Pulse server to the Pulse Collaboration meeting server and then terminate the user session on the Pulse server.

•Enable Session Sharing - Create a new user session on the Pulse Collaboration meeting server and retain the user's current session on the Pulse server.

5.Click Save Changes.

For more information on session migration, see the Pulse Secure Client Administration Guide located on the Pulse Secure support site.

Pulse Collaboration Meeting Server Use Cases

This topic describes several scenarios of starting a meeting where the Pulse server and Pulse Collaboration meeting server may or may not be the same. For these use cases, assume the following server configurations:

Server Name	Server Type	Additional Configuration
Server 1	Pulse Collaboration meeting server and allows active VPN sessions	Server 1 is configured for session sharing with Server 2, and the user authentication realms are the same between Server 1 and Server 2.
Server 2	Pulse Collaboration meeting server only	Server 1 is configured for session sharing with Server 2, and the user authentication realms are the same between Server 1 and Server 2. Server 2 is configured for session sharing with Server 3 using IF-MAP, and the authentication realms for the user are same between Server 2 and Server 3.
Server 2	Pulse Collaboration meeting server only
Server 3	Allows only active VPN sessions (is not a Pulse Collaboration meeting server)	Server 2 is configured for session sharing with Server 3 using IF-MAP, and the authentication realms for the user are same between Server 2 and Server 3.
Server 4	Pulse Collaboration meeting server and allows active VPN sessions	No session sharing with any other server.

Use Case: User has an active VPN Session on Server 1 and starts a meeting on Server 1

Pulse uses the user's existing VPN session credentials to SSO the user in to the Pulse Collaboration meeting server. The Meeting web page appears (same as clicking the Meeting button on the end-user's secure gateway home page) and the user starts a meeting. The user is not logged out of the Pulse Collaboration meeting server when they end the meeting since this is a shared server. The meeting server sign out option on the Pulse tray menu is disabled. If the user attempts to disconnect from Pulse while the meeting is active, a warning message alerts the user that disconnecting from the Pulse server will end their meeting.

Use Case: User has an active VPN Session on Server 1 and starts a meeting on Server 2

When the user starts the meeting on Server 2, Pulse uses the user's credentials on Server 1 to SSO in to Server 2. The Meeting web page appears (same as clicking the Meeting button on the end-user's secure gateway home page) and the user starts a meeting. The user can also sign out of Server 1 while their meeting is still active, and the meeting will not disconnect. The user is not logged out of Server 2 when they end the meeting. The user can manually disconnect Server 1 or from Server 2 through the Pulse tray menu. Signing out on one server has no effect on the other server.

Use Case: User has an active VPN Session on Server 3 and starts a meeting on Server 1

Since Server 3 has session sharing only with Server 2, the option to start a meeting on Server 1 is disabled. In this case, the user can start a meeting only on Server 2.

Use Case: User has an active VPN Session on Server 3 and starts a meeting on Server 2

When the user starts the meeting on Server 2, Pulse uses the user's credentials on Server 3 to SSO in to Server 2. The Meeting web page appears (same as clicking the Meeting button on the end-user's secure gateway home page) and the user starts a meeting. The user can also sign out of Server 3 while their meeting is still active, and the meeting will not disconnect. The user is not logged out of Server 2 when they end the meeting. The user can manually disconnect Server 3 or from Server 2 through the Pulse tray menu. Signing out on one server has no effect on the other server.

Use Case: User has no active VPN session and starts a meeting on Server 1

When the user starts the meeting on Server 1, they are prompted to log in. The Meeting web page appears (same as clicking the Meeting button on the end-user's secure gateway home page) and the user starts a meeting. The user is not logged out of the Pulse Collaboration meeting server when they end the meeting since this is a shared server. The meeting server sign out option on the Pulse tray menu is disabled. If the user attempts to disconnect from Pulse while the meeting is active, a warning message alerts the user that disconnecting from the Pulse server will end their meeting.

Use Case: User has no active VPN session and starts a meeting on Server 2

When the user starts the meeting on Server 2, they are prompted to log in. The Meeting web page appears (same as clicking the Meeting button on the end-user's secure gateway home page) and the user starts a meeting. The user has to re-enter their credentials if they try to log in to Sever 1, Server 3 or Server 4. The user is not logged out of the Server 2 when they end the meeting. They can, however, manually disconnect from Server 2 through the Pulse tray menu.