I was going through some of my notes the other day and I stumbled across the following chart that I thought I'd share. I put this chart together for a coworker that had asked me about some of the advantages and disadvantages when using different account types with FTP.
This list is obviously not all-inclusive, but it should give you some things to consider when choosing which types of accounts to use for your FTP users.
One last note - all of these account types will work with FTP's User Isolation, so you can restrict any of these user accounts to specific content areas within your FTP site.
Hi Robert, I´ve a problem with ASP.NET Membership Users for FTP, here is my scenary:
We have a web app that uses Oracle Membership Provider that works without a problem, but We need to add an FTP that uses the same users. So We followed this walkthrough that You wrote (www.iis.net/.../configuring-ftp-with-net-membership-authentication-in-iis-7) that worked great on IIS 7. But on IIS 8 it simply doesn´t work, the error shows: Default Membership Provider could not be found. So, is there a way to do this on IIS 8 ?
The Web app works fine in both IIS 7 and 8.
Thanks in advance.
I´ve solved my problem using your walkthrough www.iis.net/.../how-to-use-managed-code-c-to-create-a-simple-ftp-authentication-provider but cause I need to use the Oracle database users, I've implemented IFtpAuthenticationProvider like this:
Return Membership.ValidateUser(userName, userPassword);
But that gave me the same error: Default Membership Provider could not be found. But if I create an instance of the provider like this:
MembershipProvider m = Membership.Providers("OracleMembershipProvider");
Return m.ValidateUser(userName, userPassword);
Everything works as expected. Is IIS 8 loading the providers in a different way? I hope Microsoft could solve this strange behaviour.