Change SSL to TLS.

Author: TimShererWithAquent

docs/reporting-services/report-design/add-change-or-delete-a-map-or-map-layer-report-builder-and-ssrs.md

@@ -216,7 +216,7 @@ ms.author: maggies
 
 3.  In the Properties pane, set UseSecureConnection to **True**.  
 
- The connection for the Bing Maps Web service will use the HTTP Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), service to retrieve Bing map tiles for this layer.  
+ The connection for the Bing Maps Web service will use the HTTP SSL service to retrieve Bing map tiles for this layer. Transport Layer Security (TLS) was previously known as Secure Sockets Layer (SSL).
 
 ##  <a name="Language"></a> To specify the language for tile labels  
 

docs/reporting-services/reporting-services-data-alerts.md

@@ -267,7 +267,7 @@ The following summarizes the key areas of [!INCLUDE[ssRSnoversion](../includes/s
  [!INCLUDE[ssRSnoversion](../includes/ssrsnoversion-md.md)] provides performance counters for other [!INCLUDE[ssRSnoversion](../includes/ssrsnoversion-md.md)] features. For more information, see [Performance Counters for the ReportServer:Service  and ReportServerSharePoint:Service Performance Objects](../reporting-services/report-server/performance-counters-reportserver-service-performance-objects.md), [Performance Counters for the MSRS 2011 Web Service and MSRS 2011 Windows Service Performance Objects (Native Mode)](../reporting-services/report-server/performance-counters-msrs-2011-web-service-performance-objects.md), and [Performance Counters for the MSRS 2011 Web Service SharePoint Mode and MSRS 2011 Windows Service SharePoint Mode Performance Objects (SharePoint Mode)](../reporting-services/report-server/performance-counters-msrs-2011-sharepoint-mode-performance-objects.md).  
 
 ##  <a name="SupportForSSL"></a> Support for TLS  
- [!INCLUDE[ssRSnoversion](../includes/ssrsnoversion-md.md)] can use the HTTP Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), service to establish encrypted connections to a report server or SharePoint site.  
+ [!INCLUDE[ssRSnoversion](../includes/ssrsnoversion-md.md)] can use the HTTP SSL service to establish encrypted connections to a report server or SharePoint site. Transport Layer Security (TLS) was previously known as Secure Sockets Layer (SSL).
 
  The alerting runtime service and data alerts user interface support TLS and works similarly whether you use TLS or HTTP; however, there are some subtle differences. When the data alert definition is created using and TLS connection, the URL that links back to the SharePoint library from the data alert message also uses TLS. You can identify the TLS connection because it uses HTTPS instead of HTTP in its URL. Likewise, if the data alert definition was created using an HTTP connection, the link back to the SharePoint site uses HTTP. Whether the alert definition was created using TLS or HTTP, the experience for users and alerting administrators are identical when using Data Alert Designer or Data Alert Manager. If the protocol (HTTP or TLS) should change between the time that the alert definition was created and then updated and resaved, the original protocol is kept and used in link URLs.  
 

docs/reporting-services/security/configure-ssl-connections-on-a-native-mode-report-server.md

@@ -1,5 +1,5 @@
 ---
-title: "Configure SSL Connections on a Native Mode Report Server | Microsoft Docs"
+title: "Configure TLS Connections on a Native Mode Report Server | Microsoft Docs"
 ms.date: 05/14/2019
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
@@ -13,11 +13,11 @@ ms.assetid: 212f2042-456a-4c0a-8d76-480b18f02431
 author: maggiesMSFT
 ms.author: maggies
 ---
-# Configure SSL connections on a native mode report server
-  [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Native mode uses the HTTP SSL (Secure Sockets Layer) service to establish encrypted connections to a report server. If you have certificate (.cer) file installed in a local certificate store on the report server computer, you can bind the certificate to a [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] URL reservation to support report server connections through an encrypted channel.  
+# Configure TLS connections on a native mode report server
+  [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Native mode uses the HTTP SSL (Secure Sockets Layer) service to establish encrypted connections to a report server. Transport Layer Security (TLS) was previously known as Secure Sockets Layer (SSL). If you have certificate (.cer) file installed in a local certificate store on the report server computer, you can bind the certificate to a [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] URL reservation to support report server connections through an encrypted channel.  
 
 > [!TIP]  
->  If you are using [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode, see SharePoint documentation for more information. For example [How to enable SSL on a SharePoint 2010 web application](https://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-ssl-on-a-sharepoint-web-application.aspx).  
+>  If you are using [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode, see SharePoint documentation for more information. For example [How to enable TLS on a SharePoint 2010 web application](https://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-ssl-on-a-sharepoint-web-application.aspx).  
   
  Because Internet Information Services (IIS) also uses HTTP SSL, there are significant interoperability issues that you must account for if you run IIS and [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] on the same computer. Be sure to review the Interoperability Issues with IIS section for guidance on how to address these issues.  
 
@@ -29,26 +29,26 @@ ms.author: maggies
  If you are running IIS and [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] together on the same computer, you can use the IIS Manager console application to get the certificate installed on your computer. IIS Manager includes options for creating and packaging a certificate request (.crt) file for subsequent processing by a trusted certificate authority. The certificate authority that you are using will generate a certificate (.cer) file and send it back to you. You can use IIS Management console to install the certificate file in the local store. For more information, see [Using SSL to Encrypt Confidential Data](https://go.microsoft.com/fwlink/?LinkId=71123) on Technet.  
 
 ## Interoperability issues with IIS  
- The presence of IIS on the same computer as [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] will significantly affect SSL connections to a report server:  
+ The presence of IIS on the same computer as [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] will significantly affect TLS connections to a report server:  
 
--   If IIS is installed, the World Wide Web (W3SVC) service must always be running. The HTTP SSL service will make a dependency on IIS if it detects that IIS is running. This means that the World Wide Web service (W3SVC) must be running whenever IIS and [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] are installed on the same computer and you are configuring report server URLs for SSL connections.  
+-   If IIS is installed, the World Wide Web (W3SVC) service must always be running. The HTTP SSL service will make a dependency on IIS if it detects that IIS is running. This means that the World Wide Web service (W3SVC) must be running whenever IIS and [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] are installed on the same computer and you are configuring report server URLs for TLS connections.  
 
--   Uninstalling IIS can temporarily disrupt service to an SSL-bound report server URL. For this reason, it is recommended that you restart the computer after you uninstall IIS.  
+-   Uninstalling IIS can temporarily disrupt service to an TLS-bound report server URL. For this reason, it is recommended that you restart the computer after you uninstall IIS.  
 
-     Rebooting the computer is necessary to clear all SSL sessions from cache. Some operating systems cache SSL sessions up to 10 hours, causing an https:// URL to continue to work even after the SSL binding has been removed from the URL reservation in HTTP.SYS. Rebooting the computer closes any open connections that use the channel.  
+     Rebooting the computer is necessary to clear all TLS sessions from cache. Some operating systems cache TLS sessions up to 10 hours, causing an https:// URL to continue to work even after the TLS binding has been removed from the URL reservation in HTTP.SYS. Rebooting the computer closes any open connections that use the channel.  
 
-## Bind SSL to a reporting services URL reservation  
+## Bind TLS to a reporting services URL reservation  
  The following steps do not include instructions for requesting, generating, downloading, or installing a certificate. You must have a certificate installed and available to use. The certificate properties that you specify, the certificate authority you obtain it from, and the tools and utilities you use to request and install the certificate are up to you.  
 
  You can use the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool to bind the certificate. If the certificate is installed correctly in the local computer store, the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool will detect it and display it in the **SSL Certificates** list on the **Web Service URL** and **Web Portal URL** pages.  
 
-### To configure a report server URL for SSL  
+### To configure a report server URL for TLS  
 
 1.  Start the Reporting Services Configuration tool and connect to the report server.  
 
 2.  Select **Web Service URL**.  
 
-3.  Expand the list of SSL Certificates. [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] detects server authentication certificates in the local store. If you installed a certificate and you do not see it in the list, you might need to restart the service. You can use the **Stop** and **Start** buttons on the **Report Server Status** page in the Reporting Services Configuration tool to restart the service (top page).  
+3.  Expand the list of TLS/SSL Certificates. [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] detects server authentication certificates in the local store. If you installed a certificate and you do not see it in the list, you might need to restart the service. You can use the **Stop** and **Start** buttons on the **Report Server Status** page in the Reporting Services Configuration tool to restart the service (top page).  
 
 4.  Select the certificate.  
 
@@ -58,7 +58,7 @@ ms.author: maggies
 
  Report server database configuration is a requirement for testing the URL. If you have not yet created the report server database, do so before testing the URL.  
 
- URL reservations for Web Portal URL and the Report Server Web Services URL are configured independently. If you want to also configure the web portal access through an SSL-encrypted channel, continue with the following steps:  
+ URL reservations for Web Portal URL and the Report Server Web Services URL are configured independently. If you want to also configure the web portal access through an TLS-encrypted channel, continue with the following steps:  
 
 1.  Access the **Web Portal URL**.
 
@@ -74,11 +74,11 @@ ms.author: maggies
  Certificate bindings will be stored in HTTP.SYS. A representation of the bindings you defined will also be stored in the **URLReservations** section of the RSReportServer.config file. The settings in the configuration file are only a representation of actual values that are specified elsewhere. Do not modify the values in the configuration file directly. The configuration settings will appear in the file only after you use the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool or the Report Server Windows Management Instrumentation (WMI) provider to bind a certificate.  
 
 > [!NOTE]  
->  If you configure a binding with an SSL certificate in [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] and you later want to remove the certificate from the computer, make sure to remove the binding from [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] before you remove the certificate from the computer. Otherwise, you will be unable to remove the binding by using the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool or WMI and you will receive an "Invalid parameter" error. If you have already removed the certificate from the computer, you can use the Httpcfg.exe tool to remove the binding from HTTP.SYS. For more information about Httpcfg.exe, see the Windows product documentation.  
+>  If you configure a binding with an TLS/SSL certificate in [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] and you later want to remove the certificate from the computer, make sure to remove the binding from [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] before you remove the certificate from the computer. Otherwise, you will be unable to remove the binding by using the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration tool or WMI and you will receive an "Invalid parameter" error. If you have already removed the certificate from the computer, you can use the Httpcfg.exe tool to remove the binding from HTTP.SYS. For more information about Httpcfg.exe, see the Windows product documentation.  
   
- SSL bindings are a shared resource in Microsoft Windows. Changes made by [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager or other tools like IIS Manager can impact other applications on the same computer. It is a best practice to use the same tool to edit bindings that you used to create the bindings.  For example if you created SSL bindings using Configuration Manager, then it is recommended you use Configuration Manager to manage the life cycle of the bindings. If you use IIS manager to create bindings, then it is recommended you use IIS manager to manage the life cycle of the bindings. If IIS is installed on the computer before [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] is installed, it is a good practice to review the SSL configuration in IIS before configuring [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)].  
+ TLS bindings are a shared resource in Microsoft Windows. Changes made by [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager or other tools like IIS Manager can impact other applications on the same computer. It is a best practice to use the same tool to edit bindings that you used to create the bindings.  For example if you created TLS bindings using Configuration Manager, then it is recommended you use Configuration Manager to manage the life cycle of the bindings. If you use IIS manager to create bindings, then it is recommended you use IIS manager to manage the life cycle of the bindings. If IIS is installed on the computer before [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] is installed, it is a good practice to review the TLS configuration in IIS before configuring [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)].  
 
- If you remove SSL bindings for [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] using the Reporting Services Configuration Manager, SSL may no longer work for Web sites on a server that is running Internet Information Services (IIS) or on another HTTP.SYS server. [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager removes the following registry key: **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo\0.0.0.0:443** When this registry key is removed, the SSL binding for IIS is also removed. Without this binding, SSL is not provided for the HTTPS protocol. To diagnose this issue, use IIS Manager or the HTTPCFG.exe command line utility. To resolve the issue, restore the SSL binding for your web sites using IIS Manager. To prevent this issue in the future, use IIS Manager to remove the SSL bindings and then use IIS Manager to restore the binding for the desired Web sites. For more information, see the knowledge base article [SSL no longer works after you remove an SSL binding (https://support.microsoft.com/kb/956209/n)](https://support.microsoft.com/kb/956209/n).  
+ If you remove TLS bindings for [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] using the Reporting Services Configuration Manager, TLS may no longer work for Web sites on a server that is running Internet Information Services (IIS) or on another HTTP.SYS server. [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Configuration Manager removes the following registry key: **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo\0.0.0.0:443** When this registry key is removed, the TLS binding for IIS is also removed. Without this binding, TLS is not provided for the HTTPS protocol. To diagnose this issue, use IIS Manager or the HTTPCFG.exe command line utility. To resolve the issue, restore the TLS binding for your web sites using IIS Manager. To prevent this issue in the future, use IIS Manager to remove the TLS bindings and then use IIS Manager to restore the binding for the desired Web sites. For more information, see the knowledge base article [SSL no longer works after you remove an SSL binding (https://support.microsoft.com/kb/956209/n)](https://support.microsoft.com/kb/956209/n).  
 
 ## See also  
  [Authentication with the Report Server](../../reporting-services/security/authentication-with-the-report-server.md)