|
|
|
If you wish to store your file attachments on a remote file server accessed via a UNC share (such as \\fileServer\attachments), additional configuration may be necessary.
If you try to upload a file attachment, you may encounter a Permission Denied error (from the attachment2.asp page).
This can happen because the anonymous IIS user does not have permission to access the remote file share, such as \\fileServer\attachments.
We want the user that is executing the web app to be able to write to that remote directory. Here's one way to set this up.
Lets say we have a user called mydomain\dovetail_app
On the \\fileServer, be sure that the domain user has read and write permissions to the attachments directory. This is best achieved by setting the NTFS permissions (as opposed to setting permissions on the share itself).
We can then set the Identity of the Application Pool to this user. Right-click on the application pool, and choose Advanced Properties. Set the Identity to be the domain user.
Make sure your Dovetail Agent web application belongs to the application pool.
Click the Authentication icon for the application. Right-click on the Anonymous Authentication item. Set the Anonymous Authentication Credentials to be the Application Pool Identity.
Now, the app will run as the same user as the application pool, which is the domain user that we configured the app pool identity as earlier.
You should now be able to successfully upload file attachments.
When downloading a file attachment, the Dovetail Agent application transforms the physical file path into a URL with the help of Dovetail Seeker. For actual download, the URL refers to Dovetail Seeker Proxy for access to the file, but it is Dovetail Seeker which needs to access the file.
See Also |
Next |