Security and Internet Applications

Security for DHTML Applications

DHTML applications are affected by security in the following ways:

You may encounter zone security in Internet Explorer 4.x when you attempt to download your DHTML application to a client. For an explanation of security zones, see the Internet Client SDK, available on your MSDN CD.
When you deploy your DHTML application, you must make sure the deployment files are properly signed and licensed. For more information, see the "Downloading ActiveX Components" chapter.

Security for IIS Applications

IIS applications face the same restrictions listed for DHTML applications in the section above. In addition, IIS applications have additional security options based on the fact that all IIS applications use an Active Server Page (ASP) as the entry point into the application. You can secure an ASP page in several ways:

You can set permissions on the virtual directory on your Web server that contains the ASP page.
You can set file access permissions, if you are using the Windows NT File system (NTFS) to determine which users can access the ASP page.
You can use client certificates through two protocols known as Secure Sockets Layer (SSL) 3.0 or through Private Communications Technology (PCT). A client certificate is an encrypted number the browser sends to the server when it requests the ASP page.

For More Information See "An Introduction to Webclasses" in "Developing IIS Applications" for more information on the relationship between IIS applications and ASP pages.