Authentication of publishers is handled by any mechanism that is exposed by Windows NT on the server that matches the authentication method supported by the client-side software; for example, Basic/NTLM/MSN/DPA (Distributed Password Authentication) or Microsoft Membership System.
Note
Posting Acceptor specifically disallows anonymous connections.
IIS and PWS enumerate supported authentication methods and negotiate with the client to find a match. You can control who is allowed to post to a given site by establishing accounts for those users on the server. You can also control which directories those users can post to by applying access control lists (ACLs) to the various destination directories for that site. For more information about applying ACLs to a destination directory, see the Windows NT and Windows 95 user guides.
Your client’s publishing software can authenticate against your Web server to upload their files using Microsoft Membership System or any other authentication mechanisms supported by Microsoft Internet Information Server (IIS), Peer Web Services, and Personal Web Server.
If you have installed a Security Certificate on your Web server, your publishers are able to upload their files securely via HTTPS (Hypertext Transfer Protocol Secure) assuming that the client supports SSL (Secure Sockets Layer).