We have a PHP application running on a LAMP-machine. But one of our clients persists on using Windows as their OS.

Apache on Windoz > works fine of course.
PHP > no problems.
Mysql > everything under control.

However our PHP application enables its users to upload HTML documents. On our LAMP system we are running a ProFTPD server, and for each new "proofreading project" a new Linux user is created through a shell script, called from PHP (i.e. a /home directory with an FTP upload directory recognized by ProFTPD is created).

Creating directories on a Windows machine isn't a big deal with PHP. But... what about the FTP server and FTP users???

There's loads of nifty little Windows FTP deamons (like Cerberus, Guild, War etc.). But all of these have there OWN user management.
How can I somehow create an FTP user with a password, "give" that user access to a freshly created directory somewhere in a safe location on a Windows machine, through a script, called from PHP?

One solution would be to use the same FTP user and password, but that would mean all PHP application users would have access to all projects.

I'm probably overlooking some very basic Windows user issues... Or getting rid of Apache and switching over to IIS + IIS FTP?

Feedback appreciated mucho!!

    As much as I hate to say it, I think the best move would be to switch over to IIS + IIS FTP. Aside from the fact that most Windows FTP daemons use their own user management, most them also have quite large security holes.

    Why are people so insistent on Microsoft? You give them all the evidence in the world to support *nix and Open Source over MS proprietry crap, and the simple fact that it's free puts them off. "Anything that's free can't be a good product". bah!

      Well, thanks for the reply.

      Look, you're absolutely right on the open source thing!! We do most stuff on Linux + PHP etc.

      But I work for a Japanese company, with Japanese clients... and when the management decides SOMETHING - even when it's the biggest waste of money and time to accomplish an utterly rediculous objective - it's got to be done.

      I am not an expert on IIS / Windows platform. So any ideas on configuring IIS FTP then?

      thnx

        I don't claim to be a Sambar Server expert, but I do know the pro version for Windows includes integrated FTP and mail services. www.sambar.com

          I'm not really familiar with Sambar... browsing through Sambar's documentation, its FTP capabilities seem just as limited as the ones I mentioned before. Is Sambar capable of interpreting *.sh scripts?

          I understand there are two possibilities: find an FTP server (with possible security holes) that enables FTP users to be created through a script, or use Windows users for IIS FTP.
          Is it possible to create a new Windows user through some kind of script (Windows scripting)? If so, how do give that new Windows user access to a certain directory in the IIS FTP - without needing the help of a sysadmin?

            Write a Reply...