Adobe 65015459 Server Guide - Page 15

ADOBE CONTRIBUTE CS3

User Guide

12

Understanding server access for connecting to CPS-managed websites

As an administrator, you should require that users enter their own account username and password to log in when

they use FTP, SFTP, or WebDAV to connect to a website managed by CPS. This is a best practice and the default

option. The alternative is to use a shared FTP, SFTP, or WebDAV account for a website connection managed by CPS.

Requiring users to log in with their own account username and password provides an extra layer of security. When

you share a website connection that uses a shared account, the username and password for the shared account are

stored on the machine where CPS is installed. The password is stored as a hash of the password in a non-browsable

folder, and you can restrict access to this folder. However, the password could be at risk if it is not a strong password.

Therefore, it is recommended that you not use shared account information for any CPS website connection, but that

you require users to log in with their own account information.

If you require users to log in with their own account information, CPS prompts them for a username and password.

You can improve the user experience by creating FTP, SFTP, or WedDAV accounts tied to your user directory service

so that users do not have to know or remember another password. If the CPS login is also tied to your user directory

service, CPS can automatically reuse the user’s CPS login information to open the connection and does not prompt

for a second password for connection information. The user also can have Contribute remember the account

username and password for future use.

As an administrator for a website managed by CPS, you can view or modify FTP, SFTP, and WebDAV settings by

editing the connection.

For more information about editing website connections, see Contribute Help.

Restricting access to administrative folders and special file types

Access to administrative folders and special file types is restricted as a security measure.

When you create a site connection, Contribute creates special files that are stored in folders whose names begin with

an underscore (such as _mm, _baks, and _notes). These folders may contain files with user names, e-mail addresses,

previous versions of web pages, and other types of meta information used by Contribute. The underscore allows

Dreamweaver from Adobe and Contribute to distinguish between those folders and the other folders in your site.

Contribute and Dreamweaver use this naming convention to filter these special files and prevent them from

appearing in the Dreamweaver Site panel and in the Contribute Remote File Browser. These hidden folders can’t be

browsed, overwritten, or inadvertently altered by users. Additionally, some search engines and automated programs

are designed not to return pages found in folders whose names begin with an underscore.

To ensure that these folders and files remain protected, review the configuration of your web server software and

make certain that you block HTTP access to folders whose names begin with an underscore (_mm, _baks, and

_notes), the MMWIP folder, and files identified by the file extensions .lck, .mno, .bak, .lbi, .csi, and .dwt.

In particular, you might want to block HTTP access to the MMWIP folder. The MMWIP folder contains interim

drafts of files (works in progress) that you might want to protect. Adobe recommends that you restrict access to the

MMWIP folder so that only members of your organization can browse files in that folder.

Note:

In addition to using the computer’s operating system and web server software configuration settings, you might

consider using a third-party URL scanner to block HTTP access to secure these files and folders.

Apache web servers

If your website uses Apache, you can explicitly disable browsing folders and files that begin with an underscore. If

you know how to modify the Apache web server’s httpd.conf file and have permission to do so, you can use the Direc-

toryMatch directive to prevent visitors from viewing any file in a folder beginning with an underscore.

Section	Page
Contents	3
Chapter 1: Overview	4
Understanding Contribute user management models	4
Using Contribute Publishing Server with Contribute	5
Common website configurations	7
Deploying Contribute for a single website with one web server	7
Deploying Contribute for multiple websites on one web server	8
Deploying Contribute to a staging server and a live server	9
Deployment roles and responsibilities	11
Deployment tasks checklist	12
Chapter 2: Setting up your Contribute Server Environment	14
Preparing your web server before you deploy	14
Understanding network and server permissions	14
Understanding server access for connecting to CPS-managed websites	15
Restricting access to administrative folders and special file types	15
Apache web servers	15
Microsoft IIS web servers	16
Other web servers	16
Special files created by the draft review process	16
Planning your Contribute site structure and connection path	18
Understanding Contribute connection paths	18
Understanding subsites and overlapping website connections	19
Understanding Contribute network connection types	21
Network paths and web addresses (URLs)	24
Installing Contribute and creating an administrative connection	24
Preparing to connect to a website	24
Creating a Contribute website connection	25
Installing Contribute Publishing Server (Optional)	26
Software requirements	26
Installing Contribute Publishing Server using the Simple Installation	26
Installing Contribute Publishing Server by using the WAR File Installation	28
Chapter 3: Configuring Contribute	34
Configuring Contribute	34
About Contribute administrative settings	34
Configuring Contribute administrative settings	35
About Contribute user roles and settings	36
Creating Contribute roles	38
Configuring Contribute Publishing Server (CPS only)	40
Understanding Contribute user authentication models	40
About Contribute and LDAP or Active Directory	41
Authentication workflow	42
Configuring CPS User Directory and other services	43
Enabling Contribute websites to work with CPS (CPS only)	45
Adding users to your website (CPS only)	47
Deploying Contribute and website connections	49
Sending connection keys for websites	50
Sending connections for CPS managed sites	52
Deploying Contribute across an organization	52
Deploying Contribute CS3 by using Microsoft Systems Management Server	52
Uninstalling Contribute CS3	56
Index	57
A	57
about CPS 2	57
Add Users dialog box 45	57
Administer Website dialog box 43, 44	57
administration	57
settings, about 31	57
sitewide settings 32	57
administrator, responsibilities 8	57
C	57
child website 16	57
compressed WAR archive 27	57
connecting to a website that CPS manages 47, 49	57
connection key, sending 47	57
Connection Wizard 21	57
connections	57
about 18	57
child websites 16	57
creating a website 21	57
network path 22	57
overlapping 16	57
SFTP 19	57
URL 22	57
WebDAV 20	57
Contribute 45	57
Administer Website dialog box 43, 44	57
Enable Publishing Server dialog box 43	57
Log service 2	57
Publishing Server, enabling 42	57
User Directory, enabling 43	57
Contribute Publishing Server	57
about 2	57
case study 2	57
Simple Installation 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
CPS	57
about 2	57
Simple Installation 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
D	57
deploying	57
responsibilities 8	57
tasks 9	57
E	57
E-mail Notification, about 2	57
Enable Publishing Server dialog box 43	57
expanded WAR archive 27	57
F	57
FTP, connection information 22	57
I	57
installing	57
Contribute Publishing Server, Simple Installation 23	57
Contribute Publishing Server, WAR File Installation 23, 25	57
L	57
LDAP, using secure LDAP with User Directory 42	57
Log service, about 2	57
N	57
network	57
about 11	57
connection types, about 18	57
path and web addresses 21	57
O	57
overlapping, website connections 16	57
P	57
parent website 16	57
permissions, about 11	57
Publishing Server	57
enabling with Contribute 42	57
Publishing Server Console 40	57
Simple Installation 23	57
system requirements 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
web address 43	57
R	57
roles	57
about 33	57
Administrator 33	57
default 33	57
example of 34	57
Publisher 33	57
Writer 33	57
S	57
secure LDAP, using with User Directory 42	57
server permissions 11	57
services	57
E-mail Notification 2	57
Log 2	57
User Directory 2	57
SFTP connection information 19, 22	57
Simple Installation, Contribute Publishing Server 23	57
Sitewide Settings dialog box 32	57
staging servers, case study 6	57
system requirements 23	57
U	57
User Directory	57
about 2	57
enable 43	57
User Directory service, using secure LDAP (LDAPS) 42	57
user management	57
about 1	57
Contribute Publishing Server 1	57
manual connections 1	57
users, connecting to a website that CPS manages 47, 49	57
W	57
WAR	57
compressed archive 27	57
expanded archive 27	57
WAR File Installation, Contribute Publishing Server 23, 25	57
Web Application Archive, see WAR.	57
WebDAV connection information 20	58
website connections	58
child websites 16	58
creating 21, 22	58
overlapping 16	58
website, address (URL) 22	58

Adobe 65015459 Server Guide - Page 15

Understanding server access for connecting to CPS-managed websites, Restricting access

Page 15 highlights