What you've described is not really an "intranet" application. If it had
been, the students would almost certainly have user accounts prior to
connecting to the application.
That said, what you want to do is certainly possible, and it can be done in
the same way on both Windows XP and 2003. There's a sample for adding a new
local user via System.DirectoryServices at
http://support.microsoft.com/default...b;en-us;306271.
Unfortunately, the 1.x versions of the.NET Framework don't include
functionality for manipulating file and folder permissions. However, you
can find a managed wrapper for the required Windows API calls at
http://www.gotdotnet.com/Community/U...f-e0705af065d9.
HTH,
Nicole
"J'son" <si*******@hotmail.com> wrote in message
news:11*********************@l41g2000cwc.googlegro ups.com...
Imagine this scenario... a small "English as 2nd language" school wants
to give students space on their web server to post html files (each
student can have a custom webspace).
When a new user registers with the site (and is confirmed to be a
student), the application is to create a new folder under the main
virtual root for their use:
http://www.mysmallschool.com/webspaces/<usernamehere>
So the student can manage files in this new folder, a new FTP virtual
directory is set up pointing to the above folder on the web server. And
finally, the student himself is given an account on the web server with
only read/write permissions to that specific FTP directory. The
application is to handle all this.
I have informed the client that I could create a special upload page
that would be much more secure (and probably easier to implement), but
they want it done this way so that students can use
FrontPage/Dreamweaver to publish their files via FTP. Grrrr....
Whew! See my dilemma? Hence my questions about Active Directory or any
other security namespace..
Thanx!
J'son
