User management for dummies

Question

Dear Supporters

I need your assitence.

We want o use your FTP Server, because of the possibility to write our own extensions with dotNet.
That works so far. I have written two authentication extension for checking a user in the a database and an event extension that do something when login, up and download is triggered.
For the moment that works fine.
But i didn't bring it to work, to handle the user managment.
My idea is, that i have a non windows user, let's call him cbtransfer, who has a homefolder like %ExternalHomeFolder%?%AutoCreate%.

In my AuthExtension in check the username and password, when a user logedin against a database. When both is correct is set authInfo.IsCorrectPassword = True and authInfo.HomeDirectory = table.homepath & "\" from a database table.
 

The windows folder for the homepath is d:\ftp\cust1

That seems to work, but ...

When i try to log in with an ftp client, with i. e. user cust1 pwd cust1 then i get the message that the dirtory list is not allowed. File uploads are not alowed too.
 

The windows permissons on the folder is set to fuul permission to everyone and the user cbtransfer has every permisson i can set to allowed.

After a couple of hours i see, that the homefolder is created und C:\Windows\SysWOW64.

So, what is the correct way to create a user, who can access the homefolder in d:\cust ???

At the moment, i have no diea who to solve the problem.

Regards
HaPe

Comments

Probably best to enable logging at the Debug level, replicate the login issue, and then open a support ticket and attached the zipped log file.
http://enterprisedt.com/support/open.php

Answer 1

I think your problem may be caused by the 'log-in-as' user not having sufficient permissions for the folder.  The log-in-as user is set in the General User Settings dialog.  By default it's defaultExtension, but you can set it to any user.  Users logging in via your custom authenticator will use the settings of the log-in-as user, so I suggest setting the owner of the folder to be this user and making sure that the owner has sufficient permissions.

Secondly, the reason why you're seeing folders created under C:\Windows\SysWOW64 is that the path defined by your macro is ending up being relative, and since the default working directory of a Windows service is C:\Windows\SysWOW64 your folder path is relative to that.  In fact, version 9.1, which is due for release within two weeks actually prevents this.  Paths defined by macros must therefore always be absolute.  In your case, if the macro is "%ExternalHomeFolder%?%AutoCreate%" then I suspect you're not setting the home directory in your extension, so please check that.