Security, in the context of an ASP.NET application, involves three fundamental operations. These operations are carried out during the lifetime of each secure ASP.NET Web application and are described as follows: More...

As mentioned earlier in this book, the .NET Framework is composed of classes—
many classes. Namespaces are used to create a hierarchical structure of all these
classes, and they help prevent naming collisions. A naming collision occurs when
two classes have the same name. Because namespaces provide a hierarchy, it’s pos-
sible to have two classes with the same name, as long as they exist in different
namespaces. Namespaces, in effect, create scope for classes. More...

Simple Object Access Protocol (SOAP) is the protocol used by client applications for send-
ing requests to and receiving responses from Web services. SOAP is a lightweight protocol
built on top of HTTP—the protocol used by the Web to send and receive HTML pages. SOAP
defines an XML grammar for specifying the names of Web methods that a consumer can in-
voke on a Web service, for defining the parameters and return values, and for describing the
types of parameters and return values. When a client calls a Web service, it must specify the
method and parameters by using this XML grammar. More...

With Forms-based security, you can verify the identity of a user by displaying a login form
that prompts the user for an ID and a password. After the user has been authenticated, the
various Web forms that make up the application can be accessed, and the user’s security
credentials can be examined by the code running in any page if additional authorization is
needed. (A user might be able to log in to the system but might not have access to every
part of the application.)  More...