上海云学科技有限公司
全国统一服务热线:021-20423996;13501955596
webex meetings

Cisco Webex Meetings

Webex视频会议 Webex Meetings


Webex旗舰产品,视频会议第一选择



24小时随时申请,免费开通

每个工作日9:00-18:00

021-20423996 13501955596

Webex 升级 XML&URL API升级for TLS1.2
来源: | 作者:yunxue | 发布时间: 2018-08-07 | 9472 次浏览 | 分享到:
为严格遵守国际安全标准,以及更好地保护用户隐私数据,Webex Meetings将于2018年10月1日进行TLS1.2(安全传输层协议1.2)的安全策略升级。此次升级适用于Webex在PC端和移动端的所有应用程序、Webex的网页版会议、以及使用API的第三方应用程序。

尊敬的客户:

为严格遵守国际安全标准,以及更好地保护用户隐私数据,Webex Meetings将于2018101进行TLS1.2(安全传输层协议1.2)的安全策略升级。此次升级适用于WebexPC端和移动端的所有应用程序、Webex的网页版会议、以及使用API的第三方应用程序。

2018101日之前,用户须要遵循下面列出的所有应用程序的最低支持版本(主持人和参会方都需遵循)。如果您有使用下列早期版本的情况,则须更新或启用TLS 1.2,以避免服务中断。(有部分用户在Webex页面已经收到TLS1.2的告警窗口,窗口中的日期是2018729日,此日期将延长至2018101日,请收到告警的用户忽略告警中的日期。)

  • Microsoft Internet Explorer


支持的最低浏览器版本为Internet Explorer 10IE10支持的最低操作系统是Windows 7,如果您使用的是早期版本的IEWindows,则需要更新。

IE浏览器启用TLS 1.2步骤:

1)     打开IE浏览器,点击工具,选择“Internet选项 选择高级选项,查看安全条目。

2)     勾选 “使用 TLS 1.1” “使用TLS 1.2”,不要勾选 “使用 SSL 3.0”

3)     选择应用,然后选择确定


  • 谷歌浏览器Chrome :支持的最低浏览器版本:65.0
  • 火狐浏览器Firefox:支持的最低浏览器版本:52.0
  • AndroidiOS:在用Webex应用加入会议时,不会出现任何中断。
  • Webex Web App应用程序如果从Webex Web App加入,浏览器须与上述最低版本一致。
  • XMLURL API:用户通过WebEx APIWebEx与他们的业务集成在一起。在强制执行TLS 1.2之后,为了构建具有相同协议的连接,用户对Webex API的应用程序调用必须使用TLS 1.2,应用程序将无法使用早于TLS 1.2的协议连接到Webex会议,具体操作请参考如下操作:


Steps for upgrading to TLS 1.2 vary for different coding languages. See details below for the three languages for which we offer SDKs: PHP, Java and .NET.


PHP:

Are you using the PHP SDK? Action required:

Yes

No action required.

 

The PHP SDK is on PHP 5.7. It uses CURL for making API calls and supports CURL version 7.54.0, which has default support for TLS 1.3.

 

Verify that your PHP version supports CURL version 7.34.0 or newer:

 

1. Use php -i to check for modules that your PHP has installed.

 

2. Find the curl section. You will see something like:

No

o   CURL

 

o   cURL support => enabled

 

o   cURL Information => 7.34.0

PHP version

cURL version

cURL version

5.6

7.34.0

TLS 1.2

7.54.0

7.54.0

TLS 1.3

JAVA:

Are you a Java developer?

Action required:

Yes

Depending on the Java version of your application environment you may or may not require changes to support TLS1.2. Please see the table below for details.

 

Java version

TLS support

TLS support

8

Available

No action required.

7

Available

Yes. You must explicitly enable TLS 1.2.

6

Available

Maybe. Java 6 supports TLS 1.2 in versions 6u115 b32 and above. If you are on a lower version, upgrade to a higher version and explicitly enable TLS 1.2.

5

No support

Yes. Upgrade to Java 6 or higher, preferably Java 8.

.NET:

The current version of the .NET SDK (v3.2.1) uses .NET Framework 4.0. We are migrating the .NET SDK (.NET SDK for QuickBooks Online V3.2.1) to Framework 4.6.1 to proactively support TLS 1.2.

After the mid-August 2017 .NET SDK release, the SDK will only support Framework 4.6.1.

Are you using the .NET SDK?

Action required:

Yes

If you are a .NET SDK developer, move your .NET application to Framework 4.6.1 and the latest SDK by Dec 31, 2017 to support TLS 1.2.

No

If you are not using the .NET SDK, move your .NET application to Framework 4.6.1 by Dec 31, 2017 to support TLS 1.2.

.NET Framework

Default TLS version supported

Timing

4.0

1.1

July 31, 2017 

4.5

1.1 is default, can be set to 1.2

July 31, 2017

4.6.1

1.2

December 31, 2017

 

What do you need to do for your .NET application?

To minimize the impact to our .NET developer community, we have prepared a migration plan to .NET Framework 4.6.1.

To move your .NET application to framework 4.6.1:

1. Open your project properties by right-clicking it.

2. Change the Target Framework to 4.6.1 under the Application tab.

- Upgrade your .NET SDK to the latest version by mid-August.

Use the NuGet Package Manager for this upgrade.

l  Note: Any developer using the .NET OAuth 2.0 lib may already be using Framework 4.6.1, as this lib supports Framework 4.6.1, at a minimum.

- Resolve any errors in your application that may arise from using the latest minor version.

The minor version mechanism is designed to be backward-compatible, but any hard-coded API response mapping can cause errors in your code. For example, your app may have a database mapping for an old QuickBooks Online schema if you haven’t updated the .NET SDK in a long time, and might not support new fields in newer minor versions.

l  Note: Minor versions provide support for additional new fields in the QuickBooks Online API schema. You can read more details about minor versions here. This table provides a mapping of all .NET SDK versions and the supported minor versions.

.NET SDK version

Highest supported minor version

V3DotNetSDK2.0.1

NA

V3DotNetSDK2.0.2

NA

V3DotNetSDK2.0.4

NA

V3DotNetSDK2.0.5

NA

V3DotNetSDK2.1.0

NA

V3DotNetSDK2.1.1

1

V3DotNetSDK2.3.0

2

V3DotNetSDK2.4.0

3,4

V3DotNetSDK2.5.0

5

V3DotNetSDK2.6.0

6

V3DotNetSDK2.7.0

7

V3DotNetSDK2.8.0

8

V3DotNetSDK2.9.0

8

V3DotNetSDK3.0.0

9,10,11

V3DotNetSDK3.1.0

9,10,11

Benefits of moving to the latest version:

l  Your .NET application will be ready to support TLS 1.2, a more secure communications method than earlier versions.

l  Your application will upgrade to the latest minor version of the QuickBooks Online API schema and can take advantage of the added features and fields of the API.

l  Any .NET applications integrating with financial data along with QuickBooks Online APIs will get some lead time to meet the upcoming PCI security standards TLS 1.2 migration dates.

How to test if your application is connecting to TLS 1.2 URL successfully after the required changes:

1. Make an HTTP call to this URL from your code https://tlstest.intuit.com.

It should give you a ‘success’ response.

Or

2. Make an HTTP call to this URL from your code https://tlstest.intuit.com/1_2.json

It should give you the following json response-

{

“status”: 200,

“message”: “Success!”

}

 

联系方式:

如果您对升级安排有任何疑虑或疑问,请在升级开始前,请联系您方的Webex 客服经理。

关于我们