Overview

You can specify how long a Webex Teams for web user's session can stay idle before they're signed out. This applies to in network and off network Webex Teams for web users.

You can choose different idle timeouts for in or off network Webex Teams for web Users. Off network users are users that are deemed as not connected to your organization’s network. In network users are users that are deemed as connected to your organization's network.

Turn on Idle Session Timeout for Off Network Users are the only steps that are required if you want to use one idle session timeout for all users in your organization.

If you enter a valid cross-origin resource sharing (CORS), then you can specify different idle session timeouts for in network and off network users.

The available values that you can set for an idle timeout are:

  • 0— There is no time out and sessions remain open until the user signs out.

  • 30 minutes.

  • 1 hour. This is the default value for In and Off Network users.

  • 2 hours.

  • 4 hours.

  • 8 hours.

  • 12 hours.

Turn on Idle Session Timeout for Off Network Webex Teams for Web Users

This is the only task necessary if you want one idle session timeout to apply to all users in your organization.

1

From the customer view in https://admin.webex.com, go to Settings, and scroll to the Idle Timeouts section.

2

Turn on the switch beneath Webex Teams Web Client Idle Timeout.

3

Below Off Network, select the amount of time that off network Webex Teams for Web users can stay idle.

Turn on Idle Session Timeout for In Network Webex Teams for Web Users

1

From the customer view in https://admin.webex.com, go to Settings, and scroll to the Idle Timeouts section.

2

Turn on the switch beneath Webex Teams Web Client Idle Timeout.

3

Enter a URL that allows CORS requests from team.webex.com.

4

Below On Network, select the amount of time that on network Webex Teams for Web users can stay idle.

Testing for In Network Users

CORS is a service that allows your web server to provide resources to websites outside of your domain. When users sign in to teams.webex.com, then their browser is notified to make a CORS request to the URL that you provide. If that request succeeds, shows that they are in your network. If the request fails, teams.webex.com treats them as if they are off your network.

If you select an idle session timeout for in network Webex Teams for web users, then you must provide a URL for a web server within your network that allows CORS requests from teams.webex.com. This web server can’t be accessible from the public Internet.


CORS URLs are case sensitive.

Your CORS site needs to allow sharing with teams.webex.com. Here is an example of acceptable CORS entries in that server’s configuration:
access-control-allow-origin: teams.webex.com
or
access-control-allow-origin: *
You can use tools like postman to check or verify the access-control-allow-origin setting or this curl command:
curl -H "Origin: https://teams.webex.com" --verbose {your_CORS-enabled-site_Url}  2>&1 | grep "access-control-allow-origin" 

If the URL you enter does not allow CORS access with teams.webex.com then the in network connectivity test fails, and users will be determined to be off network, even if they are connected to your organization’s network.


Configuring a CORS URL is optional.

If you enable idle timeout for on network users and don't provide a CORS URL or the CORS URL fails the network connectivity test, then the duration you select for off network users will be applied to in network users.

For more information on adding CORS support to your server, see: https://enable-cors.org/server.html.