Support Policy Knowledge Base
- Audience Targeting for Digital Experience Platform 7.2
- AWS Cloud Services Support Policy
- Bookmarks Module for Digital Experience Platform
- Critical Incident Contact role
- Digital Experience Platform 7.0 Deprecated and Archived Items
- Digital Experience Platform 7.1 Deprecated and Archived Items
- Digital Experience Platform 7.2 Deprecated and Archived Items
- Digital Experience Platform 7.3 Deprecated and Archived Items
- Document Conversion Support Policy
- Document Repository Support Policy
- Document Thumbnails and Previews Support Policy
- Glassfish Support Policy
- Google Authorization Removal in Liferay DXP 7.2
- IBM DB2 Database Support Policy
- IBM JDK Support Policy
- Installing Archived Modules From Liferay's Public Repository
- Internet Explorer Support Policy
- Java TCK Certified OpenJDK Binaries
- JBoss Support Policy
- JDK7 Concerns
- JDK Certification, Java TCK Compliance, and Liferay
- LDAP Support Policy
- Liferay and Amazon S3 SigV2 Deprecation
- Liferay Docker Image Security Policy
- Liferay Documentum Connector for Digital Experience Platform 7.1
- Liferay DXP 2023.Q3 and DXP 2023.Q4 Transitional Support Coverage
- Liferay DXP 7.0 Fix Pack Releases
- Liferay DXP Compatibility with Elasticsearch Service on Elastic Cloud
- Liferay Security Practices
- Liferay Social Networking for Digital Experience Platform 7.1
- Liferay Web Proxy Module for Digital Experience Platform 7.1
- Linux (general) Operating System Support Policy
- Microsoft Azure Cloud Services Support Policy
- Microsoft Edge Compatibility
- Microsoft SQL Server Database Support Policy
- Mobile Device Support Policy
- MySQL Database Support Policy
- NTLM Module in Digital Experience Platform 7.2
- OpenID Removal in Liferay DXP 7.2
- Oracle Database Support Policy
- Oracle JDK Support Policy
- Oracle JRockit JDK Support Policy
- PostgreSQL Database Support Policy
- Quarterly Release Transitional Support Coverage
- Red Hat Enterprise Operating System Support Policy
- Resources Importer
- Rolling Restart - Breaking Changes
- SAML Support Policy
- Search Portlet in Liferay DXP 7.2
- Solaris Operating System Support Policy
- SSO (general) Policy
- Third-Party Paid Apps Activation Support Policy
- Tomcat Support Policy
- WebDAV Support Policy
- WebLogic Support Policy
- WebSphere Support Policy
- Wildfly Support Policy
- Xuggler Support Policy
WebDAV Support Policy
This article specifies the support policy for WebDAV integrations. WebDAV stands for Web-based Distributed Authoring and Versioning. It is a set of methods based on HTTP that allows users to create, move or delete files stored on web servers. WebDAV is supported by all major Operating Systems and desktop environments. Liferay Digital Experience Platform, Liferay Portal EE, and Liferay Commerce ("the product") have been designed with WebDAV integration. This article addresses support coverage unique to WebDAV integration, and not already covered in the generic Document Library Integrations policy.
For more information please see the Document Library Integrations policy.
Defining Support
Liferay seeks to ensure that when utilizing the product, users would be able to add, remove, access and update files in the Document Library through a WebDAV connection. Liferay will provide guidance on configuration and resolve any issues with its products when connecting to the Document Library via WebDAV.
Any issues with the operating system or third-party WebDAV client applications are the responsibility of the vendor of those applications to resolve.
Compatible Operating Systems
The WebDAV connector in the product is not tested as compatible with any third-party WebDAV client applications. Please see the Integrated Technologies Compatibility Matrix for Liferay DXP, Liferay Portal, and Liferay Commerce.
Basic or Digest Authentication
The WebDAV connector in the product requires the use of Basic or Digest authentication to access the Document Library. The product has implemented Digest authentication by default.
Digest authentication requires a user to have previously authenticated with their current password through the product’s default authentication methods in order to generate a cryptographic hash. Utilizing an alternate authentication method such as an SSO will not result in the generation of a cryptographic hash.