We are using MOSS 2007.
We are about to make one of our SharePoint sites live over the internet but we wants the file upload/download to be SFTP. Is this possible in SharePoint, if so how can this be done? Must it be done through custom code (Please provide me with an example) or is there a setting somehwere where you can turn uploads and download of the site to SFTP?
Thanks in advance!
Well SharePoint does not use FTP at all. It's files are being stored directly to database so there is no need for FTP.
By default it uses HTTP/HTTPS for file upload/download from web and WebDAV in case you are using multiple upload / explorer view.
In case you want to protect your files I would advise publishing your site via HTTPS only.
As Toni said there is no FTP or SFTP server in SharePoint (these are very different protocols).
SFTP is based on the SSH protocol which provides a similar kind of protection to what HTTPS provides. So you may be able to meet your needs by using HTTPS. You can configure this in Central Administration.
HTTPS is a lower level protocol than HTTP, and will protect both SharePoint HTTP and WebDAV traffic.
If you must use SFTP for some reason (for example integration with Unix-based systems perhaps) then you would need to run an SFTP server on the same server as SharePoint and create some mechanism for transferring these files into SharePoint. The file download process will not by fixed by this approach.
Related
Is there a way that we can set up One-Time-Password in iis?
As a web server is possible (via isapi) but i couldn't find As a ftp server
Can you elaborate how you imaging one time password with FTP?
If you care about security, you should not be using FTP at all
I've developed a solution and tested it. It's uploaded to Azure using the convenient method of publishing XML file. Now I realize that it's supposed to be put in on-premise local server (it's an internal application not requiring access to the Internet).
When I go to the server, I use the RDP to access a system. In there, I execute a connection to another RDP. The second system is the one hosting both SQL Server and IIS where the application will reside.
Is it at all possible to construct such a publish XML? If so - how? If not - what should I request form the IT department to open/install on the innermost RDP so I can shove in my stuff by the oh-my-god-I'm-so-lazy press of a button?
You must install webdeploy on your host machine. With IIS and webdeploy installed you can use same publishing techniques as you did with Azure.
I think it goes without saying that you must have direct access to host. If it's on external network you have to open webdeploy's and IIS ports, if you do not want to open this externally I recommend VPN (maybe basic point-to-point) that will create direct line between your dev and host machine.
I have a requirement, that the SharePoint portal of our company should be made accessible from internet, as in
once URL is entered in the browser, it should ask for credentials- once entered, should display the homepage of the portal.
Provided it should be accessible from the current intranet also.
It is in windows authentication mode currently.
Disclaimer: This question would be more appropriate in a forum like SuperUser or Sharepoint StackExchange. I am not a system administrator so my answer will lack detail and probably wont be optimal.
The only thing you need to provide is access from an external interface to your network. So something that routes requests from outside of your network to your sharepoint instance.
This is usually achieved through a reverse proxy and proper configuration of DNS. You can setup a reverse proxy by different means, if your organisation uses the Microsoft Stack then I suggest setting up IIS as a reverse proxy to your Sharepoint Instance. There are multiple tutorials on how to do this on the web.
http://sahelp.sharepointforall.com/FAQ/bconfigure_IIS.html
You then need to add an entry to your organisation DNS hosting something like sharepoint.organisation.com that points to your external interface (public IP) where the reverse proxy is sitting.
You will then need to add an Alternate Access Mapping to your Sharepoint WebApplication so Sharepoint can route the requests that the proxy sends to the appropriate Webapplication.
http://blog.blksthl.com/2012/12/03/a-guide-to-alternate-access-mappings-basics-in-sharepoint-2013/
If you are using basic authentication make sure you enable SSL. this can be done in several ways but a possible and easy (but not the most secure) is to enable SSL just externally and then use a normal unencrypted channel on the inside of your network, this is probably the easiest setup but again not very secure as people inside the newtork can snoop comms between the proxy and the sharepoint instance.
I have Sharepoint on the cloud and I can access it from anywhere, except home. At home I have a ClearOS and I can´t go through to my Sharepoint Portal.
I guess that I may need to open some ports, right? Whic ports?
Port 80. SharePoint runs as a normal website, unless you're trying to access Central Admin or using SharePoint Designer.
You shouldn't need to explicitly open port 80, especially if you can access other websites.
You should post more info about any errors you are getting.
Likely you need to have your Sharepoint site bypassed in the proxy server settings section. Sharepoint can use proprietary bits (ikr? Microsoft doing something proprietary?) that get borked when passing through the proxy or content filter.
If you list the site(s) in the Web Proxy module (bypass section at the bottom) it will create appropriate firewall rules that will skip over using the proxy and content filter for that site.
Cheers.
can i have multiple iis ftp sites using something similar to web site's unasigned host headers?
i have a dedicated server in a hosting facility and want to make a web site for each of my clients. to add/ remove files and content i want ftp access to each of the sites root folders.
lets say i have 10 sites set up using unasigned host headers... how can i set up 10 analogous ftp sites on the same server? AND NOT USE A DEFINED IP ADDRESS FOR EACH FTP SITE
thanks all
This is probably more suited for serverfault.
Also, I wouldn't use the built-in Windows FTP server. Check out Filezilla Server. It's free and can handle a bunch of users, sites, etc. on one IP.
Also, drop dead easy to configure.