No - you need a client license when you use Windows authentication infrastructure.
If you build an ASP.NET application that uses Forms Based AuthN, and it keeps track of all its users in an XML file (or in mySQL or something), then you don't need any CALs. Once you start using Windows AuthN, or connecting to other services that do use Windows Auth (e.g. remote file server etc), then you start needing CALs (or connector license). Cheers Ken -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Saturday, 17 May 2008 12:09 AM To: NT System Admin Issues Subject: Client licenses for web apps (was: AD in the DMZ) On Thu, May 15, 2008 at 11:32 AM, Michael B. Smith <[EMAIL PROTECTED]> wrote: > Obviously, you haven't yet thought about licensing. > Why not use application authentication instead of a/d authentication? The way I read the Microsoft licensing documentation, it doesn't matter how you authenticate the user. You need a client license (CAL or ECL) any time you individually identified a person. So even if you're running Apache and phpBB, you need a client license for every phpBB user account. The exception being if you're using Web Server Edition. Reference: "[You need a client license unless] access to the instances of server software is only through the Internet without being authenticated or otherwise individually identified by the server software or **through any other means**." (Emphasis mine.) http://www.microsoft.com/windowsserver2008/en/us/client-licensing.aspx -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
