Home > Articles > Programming > ASP .NET

This chapter is from the book

Enabling Security on MCMS

Because MCMS is so important for all types of portals, it is likely to be the first line of defense in your security scheme. The information and guidance offered in Chapter 6 apply here as well. This section provides special notes regarding security implications for MCMS. You must configure access in three locations: Internet Information Server (IIS), ASP.NET Web.config file, and the MCMS Server Configuration application. The entries you make in these locations depend on the usage scenario and your security preferences. These guidelines are for the most common scenarios.


A public web site should be available to anonymous users, with no authentication required. By default, a new MCMS site requires user authentication, even to view pages. To make your site visible to guests (anonymous users), you must change the configuration from the default as follows:

  1. In the ASP.NET Web.config file, remove or comment out the following line:

    <add type="Microsoft.ContentManagement.Web.Security. _
    CmsAuthorizationModule, Microsoft.ContentManagement. _
    Web, Version=5.0.1200.0, Culture=neutral, _
    PublicKeyToken=31bf3856ad364e35" _
    name="CmsAuthorizationModule" />
  2. In the MCMS Site Manager, create an account to use as the guest account, and add this account to the subscribers rights group.

  3. Go to the MCMS Server Configuration application in the MCMS program group and click Security.

  4. In the Guest Visitors section of the Security Configuration dialog box, click the Yes radio button for Allow Guests on Site. Enter the name of the account to use as the guest account for the site.

If you want to provide some content exclusively to authenticated users, you can follow the guidelines in the following extranet section in addition to allowing anonymous users.


Intranet sites use integrated Windows authentication. MCMS supports both Active Directory and Windows NT authentication. Integrated Windows authentication is suitable under the following conditions:

  • All users have Windows NT or Active Directory accounts.

  • The intranet is located inside the firewall.

  • The entire site requires authentication and does not allow anonymous users.

  • All users use Internet Explorer to access the intranet.

As you might imagine, Integrated Windows security is quite secure and even allows users to authenticate the servers that are attempting to authenticate them. It also spares the user from entering a username and password by using the current user information on the client computer for authentication. Of course integrated security also means one fewer username and password combination to manage for the user.


Now that you know how to handle security for an intranet and an Internet site, the case of the extranet is simple, as it is nothing more than a combination of the two, with a portion of the site allowing anonymous access along with a private, secured channel that is accessed via the Internet.

The baseline configuration for the extranet is the same as for an Internet site. Handle all the pages that are unrestricted in the same way as you would for any public site. This part of the site should support multiple browsers and not be based on browser-specific technology such as ActiveX controls.

The restricted access sections should be protected with MCMS rights groups. This means that the administrator must grant access to the user of a particular channel, folder, or gallery using the MCMS Site Manager. For instance, you could grant author rights to the legal notices section of a site to the legal department.

You may want to configure MCMS as an extranet to enable access for content managers. By doing so, you allow your site to be maintained from remote locations rather than just by users in your domain. For instance, content authors could create new pages and editors could participate in page review from home.

There are three general approaches to authentication on an extranet: forms-based authentication, digital certificates, and custom authentication schemes. You can combine these approaches with one another (for more on choosing an approach, see Chapter 6). The following examples show how you can use these authentication approaches to grant access on an extranet to MCMS administrative functions.

Forms-based authentication uses a cookie that stores a ticket indicating that a user has been authenticated. The system checks the cookie first on subsequent access attempts. You should use secure sockets layer (SSL) to protect the contents of the cookie so users cannot falsify that they have been authenticated. Remember that SSL imposes a performance penalty, so don't apply it to pages where anonymous access is granted anyway.

Forms-Based Authentication

Forms-based authentication routes unauthenticated users to an HTML form in which they enter their credentials. When authentication succeeds, a cookie is written and they are granted access to subsequent pages upon request. Chapter 6 provides examples of how to implement forms-based authentication. The basic steps are:

  1. Design a logon page in Visual Studio.NET. Define fields for the username and password along with a Submit button. Be sure to use the Password field as the control to accept the password.

  2. Right-click each of the controls dropped onto the page, and select Run As Server Control.

  3. Add the following code to the Submit1_ServerClick event handler:

    CmsAuthenticationTicket ticket;
    ticket = _
    CmsFormsAuthentication.AuthenticateAsUser _
    if( ticket != null )
        string strReturnUrl = _
        CmsFormsAuthentication.SetAuthCookie(ticket, true, _
        StringBuilder strUrl = new StringBuilder();
        Label1.Text = "Your username or password are _
        incorrect. Please re-enter your username and _
  4. Add the following code to the Page_Load handler:

        StringBuilder strSSL = new StringBuilder();
  5. Save your changes and build the solution.

Digital Certificates

Certificates are digital keys installed on a particular workstation. They contain information that uniquely identifies the user to applications accessed by the workstation. Certificates can be mapped to Active Directory or Windows domains. Users are issued certificates by a certificate-issuing authority, and these certificates are downloaded to their workstations. Windows 2000 comes with a certificate server so you can manage certificates.

The key difference between forms-based security and digital certificates is that certificate-based authentication does not require the user to enter authentication information on a login page. Authentication is more seamless and virtually invisible to the user. Therefore, certificates are more appropriate for processes that have no human user at all, such as the automation of the supply chain to post orders from a buyer to a seller.

You can set up your site so users without certificates are treated as anonymous users while those with certificates are mapped to the permissions and roles of the certificate user. You can establish unique certificates for each individual user or map many users to a single account. For more information on certificates and Windows security, see TechNet security how-tos at www.microsoft.com/technet/itsolutions/howto/sechow.asp and Michael Howard's book Designing Secure Web-Based Applications for Microsoft Windows 2000 (Microsoft Press, 2000).

Custom Authentication

The third form of authentication for extranets is custom authentication. This approach uses another directory service and maps users back to related Active Directory accounts. For instance, user information might be stored in Commerce Server for means of site personalization. Users might be authenticated by a third party such as Microsoft Passport. The custom security scheme would then look up the appropriate Active Directory account and grant permissions based on that account.

Custom authentication is the least commonly used form of the authentication approaches discussed here. This approach may be selected when there is a limited amount of content or functionality to provide to authenticated users, and the site is therefore rather simple to administer.

Although it is technically possible, I do not recommend using databases to store authentication information. Active Directory and other directory servers are more hardened to security threats.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020