Novell Vibe supports the following WebDAV authentication methods:
Basic Authentication: Username and password are encoded with the Base64 algorithm. The Base64-encoded string is unsafe if transmitted over HTTP, and therefore should be combined with SSL/TLC (HTTPS).
For more information, see Choosing Basic Authentication
in the Novell Vibe 3.2 Installation Guide.
If you plan to use Basic authentication over a non-secure connection (HTTP), you need to modify the registry on each Windows 7 client workstation, as described in Section 7.5, Allowing Basic Authentication over an HTTP Connection on Windows 7. The registry modification allows users to use WebDAV with Microsoft Office 2007. However, Microsoft Office 2010 is not supported.
Digest Authentication: Applies MD5 cryptographic, one-way hashing with usage of nonce values to a password before sending it over the network. This option is more safe than Basic Authentication when used over HTTP.
For more information, see Choosing Digest Authentication
in the Novell Vibe 3.2 Installation Guide.
Windows Authentication: Provides Windows users with a single sign-on experience, enabling users to automatically authenticate to Vibe after they are logged in to their individual workstations. Internet Information Services (IIS) provides this capability.
For more information, see Choosing Windows Authentication
in the Novell Vibe 3.2 Installation Guide.
If your Vibe system is fronted by either Novell Access Manager or Internet Information Services (IIS), you must use the designated WebDAV authentication method:
|
Product Fronting Vibe |
Designated Authentication Method |
|---|---|
|
Novell Access Manager |
If your Vibe installation is fronted by Novell Access Manager, as described in In the Vibe installation program, select on the WebDAV Authentication Method page. |
|
Internet Information Services (IIS) |
If your Vibe installation is fronted by IIS, as described in |
If you are using WebDAV functionality (either Edit-in-Place or mapping a Vibe folder) with Vibe on Windows 7 with a secure (HTTPS) connection, you need to ensure that the Vibe server certificate requirements are met. If all of the requirements are not met, various Windows 7 services fail.
The Vibe server certificate requirements are:
You must use a trusted server certificate that is accepted by Windows 7. This server certificate must be signed by a trusted certificate authority (CA) such as VeriSign or Equifax.
NOTE:You can use a self-signed certificate only if the certificate is imported into the Trusted Root Certification Authorities store on each Windows 7 client computer. For specific information on how to accomplish this, see Section 7.4, Configuring Windows 7 to Use a Self-Signed Certificate with Vibe
The trusted server certificate must be issued to a name that exactly matches the domain name of the URL that you are using it for. This means that it must match the URL of your Vibe site.
The date range for the trusted server certificate must be valid. You cannot use an expired server certificate.
If your environment does not require the use of Microsoft Office, you might consider migrating users to OpenOffice 3.1 or later as their document editor. Using OpenOffice 3.1 or later provides seamless integration between the WebDAV server and Vibe, regardless of which operating system is being used.