[DOCS-7470] Remove SAML Module in Content Services 7.3 and later vers…

…ions (#1265)

* [DOCS-7470] Remove SAML Module in Content Services 7.3 and later versions
* [DOCS-7470] Fix sentence after SAML Module removal

content-services/7.3/admin/auth-sync.md

@@ -48,8 +48,6 @@ The following table shows the authentication subsystem types supplied and the op
 
 > **Important:** Support for Microsoft Office depends on the authentication mechanism provided by the `external` subsystem. See [External authentication and SSO](#extauthsso) for more information.
 
-> **Important:** SAML Single Sign On can be used for Content Services and Alfresco Office Services. SAML Single Sign On is not fully implemented when mapping a PC network drive over WebDAV, i.e. to either `<alfresco_host>/alfresco/webdav` or `<alfresco_host>/alfresco/aos` endpoints. As a workaround, a PC user should use SAML to login to Content Services before mapping the drive, otherwise the map request may fail.
-
 > **Note:** If you're using a proxy (load balancer) with Kerberos authentication, either:
 
 * Use the `external` authentication subsystem and set up the proxy to implement `kerberos`

content-services/7.3/config/repository.md

@@ -665,7 +665,7 @@ For security reasons, configure your proxy to forward only requests to the resou
     -Dcookies.sameSite=none
     ```
 
-    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with either Alfresco Content Connector for Salesforce or the SAML Module, the share web must be secured using an HTTPS (SSL/TLS) certificate.
+    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with Alfresco Content Connector for Salesforce, the share web must be secured using an HTTPS (SSL/TLS) certificate.
 
 10. (Optional) Only required if configuring Alfresco Share.
 

content-services/7.4/admin/auth-sync.md

@@ -48,8 +48,6 @@ The following table shows the authentication subsystem types supplied and the op
 
 > **Important:** Support for Microsoft Office depends on the authentication mechanism provided by the `external` subsystem. See [External authentication and SSO](#extauthsso) for more information.
 
-> **Important:** SAML Single Sign On can be used for Content Services and Alfresco Office Services. SAML Single Sign On is not fully implemented when mapping a PC network drive over WebDAV, i.e. to either `<alfresco_host>/alfresco/webdav` or `<alfresco_host>/alfresco/aos` endpoints. As a workaround, a PC user should use SAML to login to Content Services before mapping the drive, otherwise the map request may fail.
-
 > **Note:** If you're using a proxy (load balancer) with Kerberos authentication, either:
 
 * Use the `external` authentication subsystem and set up the proxy to implement `kerberos`

content-services/7.4/config/repository.md

@@ -665,7 +665,7 @@ For security reasons, configure your proxy to forward only requests to the resou
     -Dcookies.sameSite=none
     ```
 
-    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with either Alfresco Content Connector for Salesforce or the SAML Module, the share web must be secured using an HTTPS (SSL/TLS) certificate.
+    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with Alfresco Content Connector for Salesforce, the share web must be secured using an HTTPS (SSL/TLS) certificate.
 
 10. (Optional) Only required if configuring Alfresco Share.
 

content-services/community/admin/auth-sync.md

@@ -47,8 +47,6 @@ The following table shows the authentication subsystem types supplied and the op
 
 > **Important:** Support for Microsoft Office depends on the authentication mechanism provided by the `external` subsystem. See [External authentication and SSO](#extauthsso) for more information.
 
-> **Important:** SAML Single Sign On can be used for Community Edition and Alfresco Office Services. SAML Single Sign On is not fully implemented when mapping a PC network drive over WebDAV, i.e. to either `<alfresco_host>/alfresco/webdav` or `<alfresco_host>/alfresco/aos` endpoints. As a workaround, a PC user should use SAML to login to Community Edition before mapping the drive, otherwise the map request may fail.
-
 > **Note:** If you're using a proxy (load balancer) with Kerberos authentication, either:
 
 * Use the `external` authentication subsystem and set up the proxy to implement `kerberos`

content-services/latest/admin/auth-sync.md

@@ -48,8 +48,6 @@ The following table shows the authentication subsystem types supplied and the op
 
 > **Important:** Support for Microsoft Office depends on the authentication mechanism provided by the `external` subsystem. See [External authentication and SSO](#extauthsso) for more information.
 
-> **Important:** SAML Single Sign On can be used for Content Services and Alfresco Office Services. SAML Single Sign On is not fully implemented when mapping a PC network drive over WebDAV, i.e. to either `<alfresco_host>/alfresco/webdav` or `<alfresco_host>/alfresco/aos` endpoints. As a workaround, a PC user should use SAML to login to Content Services before mapping the drive, otherwise the map request may fail.
-
 > **Note:** If you're using a proxy (load balancer) with Kerberos authentication, either:
 
 * Use the `external` authentication subsystem and set up the proxy to implement `kerberos`

content-services/latest/config/repository.md

@@ -665,7 +665,7 @@ For security reasons, configure your proxy to forward only requests to the resou
     -Dcookies.sameSite=none
     ```
 
-    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with either Alfresco Content Connector for Salesforce or the SAML Module, the share web must be secured using an HTTPS (SSL/TLS) certificate.
+    When using Share with Chromium-based browsers (such as Google Chrome or the latest releases of Microsoft Edge) with Alfresco Content Connector for Salesforce, the share web must be secured using an HTTPS (SSL/TLS) certificate.
 
 10. (Optional) Only required if configuring Alfresco Share.