Restricting certain file types

Hi,
Is there any way to restrict users from uploading certain type of files to certain folders? (In Teamsite)

Thanks in advance
-H

Edited by herald10 on 09/20/04 11:29 AM (server time).

Find more posts tagged with

Comments

Migrateduser

I don't believe this is native to TeamSite, but writing it as a custom UI shouldn't be too much hassle.

Dave

herald10

Dave,
Thanks for the response. Could you please throw some light on how to approach that?

Thanks a lot
-H

Migrateduser

Sure, you can get a file upload script (written in Perl, of course) from just about anywhere -- I like to use http://www.cgi-resources.com when I don't like to reinvent the wheel :-) or better yet, maybe someone here can post a file upload script they've used specifically with TeamSite.

Anyway, it doesn't really have to be anything special and, depending om your version of TeamSite, you can add it to one of the four menus in the TeamSite GUI or add your own menu section for tools and access it from there.

Does that help? If not, what specific "light" are you looking for?

Regards,

Dave

herald10

Dave,
Thanks for the info. But I am looking for something different. Lets say a user uploads images using launch pad or import. I would like to be able to restrict him from uploading to certain folder. Is that possible?

Thanks
-H

Migrateduser

I thought you meant restricting certain file types (i.e. ".exe"'s, etc.)

Other than basic file/directory security, you can't really limit specific users from uploading into certain folders. If you're using LDAP, you can do pretty much anything as far as security is concerned, but TeamSite relies on the file system's security settings and limitations to accomplish this.

Dave

Adam Stoller

You could potentially use autoprivate.cfg to mark specific types of files in specific paths as private - thus avoiding having them submitted (unless explicitly selected, I think?).
You could also use a workflow mechanism to surround the submission to check the file types that are associated with the task, the area and/or directory in which those files exist and (perhaps) check against a config file to see if its okay - and if not send email back to the user telling them they have to remove them from the job (or do it automatically and send email letting the user know it was done) or something along those lines.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I believe he's referring to the importing of files to the file system, not the submitting of files to workflow.

Dave

TCavanaugh

There are several ways to get files into a repository; the only real point of control you have is the workflow. If you have business logic you want to enforce, workflow are the place for it.

You could write a custom import CGI to get around the upload issue. You could disable the File System UI to prevent bypassing the import CGI. Disable, or rewrite, the rename functionality. That should get close to blocking certain extensions.

But, as someone suggested, a more efficient means of implementing business logic would be a workflow implementation. At that point the files would have been imported and possibly worked on; but you will have a means to block the transfer of the files; and have a way to communicate with the user why the operation is not allowed.

-TC

Migrateduser

I agree. I mentioned in the very top of this page (if you're viewing this in flat mode) that you can do it by using a custom UI, which I think is the only way to get around implementing a workflow for this.

Dave