My webhosting service provide me one FTP account. and user/client connect with their own id and password and access to the file on ftp on its own directories?
or simple word. how do i create multiple user for accessing thier directories on ftp?
The site is coded on php.
server apache
do the users only go though the web interface? if so create a directory for then and sanitize the inputs with php so they cannot browse under the base tree you give them.
Related
When my users are using the AD Federation single sign on server, they must go to the full path of the login. Ex: https://login.example.com/adfs/fs/SingleSignOn.aspx
Instead I am wanting them to connect to https://login.example.com, which I am wanting to be the directory for the login page. I could either move the login path to be the index file for the subdomain, or I could simply have https://login.example.com/ redirect to https://login.example.com/adfs/fs/SingleSignOn.aspx.
Is this possible to do in any way only using AD Federation? I know using IIS would be a simple solution, but these machines are not supposed to be running IIS or anything similar.
I am very new to using AD Federation and have very limited experience, so any help would be greatly appreciated.
There is no way to do this with ADFS out of the box. You will need to put a proxy infront of ADFS with a rewrite rule. As you already guessed, this should not be run on the same server as ADFS, as they should never be directly exposed to the internet. It is recommend, at the minimum, to use a web application proxy anyway.
I was wondering why FTP supports anonymous login ? Is it not a security issue that anyone can access files on a ftp server without having a real account ? And if anonymous account is a real good thing, what is its importance ?
If the publisher decided that the resource is public, anonymous access is perfectly valid. Take into account that FTP is just another network protocol as HTTP. If you are not scared about pubic http resources not sure why you should have any concern about FTP.
Historically FTP was widely used for placing files for public access, thus it had to support anonymous login. Note, that most servers don't support "no login" but require something like "Anonymous/guest" or "Anonymous/empty_password" login.
RFC 1635 describes "anonymous ftp" as follows:
Anonymous FTP is a means by which archive sites allow general access
to their archives of information. These sites create a special
account called "anonymous". User "anonymous" has limited access
rights to the archive host, as well as some operating restrictions.
In fact, the only operations allowed are logging in using FTP,
listing the contents of a limited set of directories, and retrieving
files. Some sites limit the contents of a directory listing an
anonymous user can see as well. Note that "anonymous" users are not
usually allowed to transfer files TO the archive site, but can only
retrieve files from such a site.
So, it's just a way to give the general public access to your server. To do this, you need to provide a username that everybody knows (i.e. 'anonymous') without a specific password (i.e. any e-mail address will do). But since everybody can access, you want to protect your content against changes, by enforcing heavy operating restrictions.
Using a server application with C#, how is it supposed to work when accessing users in the same domain if the authentication is only possible using:
OAuth2Authenticator interface?
I'm able to access the admin of the domain's Drive, but I'm missing the 3 legged OAuth in 2.0.
Looking at this description found at this link: https://developers.google.com/drive/delegation
Since this is not executed as a Service, and is not using Google Apps and cannot then
access: https://www.google.com/a/cpanel/mydomain
Also the IP is not known from where the machine running the server-application.
Currently I'm using: "Client ID for installed applications", and it works. But what I need is to also store files in other users in the same domain.
A other solution that works temporarily is to first store them at the admin domain account and then move them to the user domain account. But this removes the possibility to direct it to a parent/folder at the end user's drive. It will always be stored in root for that end user.
Basically what I want is following:
A Server application is running on a local machine (admin domain account can be used)
The application upload files to different users that are in the same domain, but with their own email address and also then have their own Drive.
Yes, you can do that through 2 legged oauth, which can provide domain-wide authorization.
Here are some links for your reference:
https://developers.google.com/gdata/docs/auth/oauth#2LeggedOAuth
http://support.google.com/a/bin/answer.py?hl=en&answer=2538798
I have little cPanel web server that I offer as a convenient addition to my web development/design services to my clients.
All of them use roundcube when accessing their webmail so it would be good to skip cpanel's mail app selection page.
I know how to do it for a single account by creating subdomain webmail.domainname.com and redirecting it to roundcube, but I'd like to know if there's a way to do it for all accounts on a server, instead of doing it manually.
I was searching for an option to show all
domains with your FTP client using DirectAdmin.
So I can make a user called user for example, it will make the domain user.nl
But I'm getting tired of searching the passwords for the FTP accounts day after day, so is their te possibility to do this with the admin account to get a level higher in the FTP?
So I have a structured view of all domains?