I recently ran into an installation issue that additional doentation would
have resolved. Adding more information about the required permissions on the
web server in particular with the following situation:
1) You have your public html directory shared from your Windows web server
over your local area network (LAN)
2) You provide read-only access to the network share and root directory for
Contribute users (you don't want them deleting the home page but want them to
have access to add/delete content in specific directories below the root level)
3) You want to create a connection in Contribute to your web server
If you try with the above situation, you get a message back that your
connection cannot be verified (e.g. Contribute cannot verify your connection
information. //server/share/ Please contact your administrator for
assistance). However, if you give Contribute users "create files / write data"
permission to the root directory (not delete, create directories, etc)...then
Contribute creates 3 temporary files whenever a Contribute users connects for
the first time. You can restrict them from modifying any files or folders at
the root level, but they must be able to create those temporary files or you
won't be able to create an initial connection.
This still leaves a hole in security in that any Contribute user can post a
new file to the root of the web server. I'm going to copy and paste this
message over to the enhancement request forum so that the dev team can consider
a patch or including a different mechanism for verifying connections other than
writing temporary files. Perhaps a warning that it can write temporary files
but still allowing you to create a connection in Contribute would work well.
<rant>Either way I spent way too much time on this and on the phone with
Macromedia Support. Their answer was I have to use secure FTP if I want to
have the level of security I'm looking for. My answer back was their
doentation doesn't give any specific details about the required server
security settings required to make a successful connection via LAN/Network. I
realize a fix might not be avialable until the next version, but I'm
disatisfied with the need to create this security hole for what according to
the doentation appears to be a legitamate way to connect to the web server.