jump to navigation

Change the Masterpage of the Search Center May 27, 2012

Posted by John Ruby in Microsoft, Sharepoint, Software, Solutions, Troubleshooting & Knowledge Bases.
Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
add a comment

 

This is a bit of a sticky situation. The default master is set to v4.master, but the default site page is built on a layout page which doesn’t use the default master. The layout page is assigned the master page by the Microsoft.SharePoint.Publishing.PublishingLayoutPage class, which hardcodes the master page as the custom master. There is a way to work around this and assign a different master page for the page layout, but the end result would probably not work very well.
Instead of changing the master page, I would suggest adding the top navigation bar to the page layout. This can be done by adding the following code to the SearchMain.aspx Page Layout. Edit it in Advanced Mode. Insert the following code right after this existing code (around line 100):
EXISTING CODE:
</ContentTemplate>
</SharePoint:UIVersionedContent>
<SharePoint:UIVersionedContent UIVersion="4" runat="server">
<ContentTemplate>
ADD THIS CODE:
  <div class="s4-lp s4-toplinks" style="background-image:url(/_layouts/images/selbg.png); background-repeat:no-repeat;
  repeat-x:left top; background-color:#f6f6f6; vertical-align:middle; min-height:25px; border-top:1px solid #e0e0e0;
  border-bottom:1px solid #b8babd">
         <SharePoint:AspMenu
           ID="TopNavigationMenuV4"
           Runat="server"
           EnableViewState="false"
           DataSourceID="topSiteMap"
           AccessKey="<%$Resources:wss,navigation_accesskey%>"
           UseSimpleRendering="true"
           UseSeparateCss="false"
           Orientation="Horizontal"
           StaticDisplayLevels="2"
           MaximumDynamicDisplayLevels="1"
           SkipLinkText=""
           CssClass="s4-tn"/>
         <SharePoint:DelegateControl runat="server" ControlId="TopNavigationDataSource" Id="topNavigationDelegate">
          <Template_Controls>
           <asp:SiteMapDataSource
             ShowStartingNode="False"
             SiteMapProvider="SPNavigationProvider"
             id="topSiteMap"
             runat="server"
             StartingNodeUrl="sid:1002"/>
          </Template_Controls>
         </SharePoint:DelegateControl>
     </div>
I grabbed the inline styles from corev4.css. You can change those as you please to get your desired look. Also, if you’d rather have all of the pages with minimal.master inlcude the top link, you can add the nop nav to minimal.master instead. Look at v4.master for the placeholder tags that I had to remove for insertion in the page layout. (asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server"> and <asp:ContentPlaceHolder id="PlaceHolderHorizontalNav" runat="server">).

Change the masterpage of the search center

Advertisements

Windows NT Security Systems March 2, 2012

Posted by John Ruby in Archives, Security, Technologies.
Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
add a comment

Windows NT Security Systems

The starting point for strong Internet security is the operating system of any machine connected to it. Fortunately for the organizations using IIS 4.0, strong levels of security were built into the core of Windows NT in order to meet and exceed certifiable security standards, i.e. the C2 security guidelines required by the U.S. Department of Defense’s evaluation criteria. Windows NT security contrasts sharply with the thin and weak security layers that are bolted on to the top of some other operating systems.

Compliance with the C2 security standard was originally only required for government organizations. However, many commercial organizations are demanding the same level of security, and they recognize the value that such standards offer. The main requirements for C2 compliance are:

  • User identification and authentication. Before gaining access to the systems, a user must prove their identity. This is typically done by providing a user-id / password combination, for example by entering the details via a keyboard or by the presentation of a device such as a smart card which stores such information.
  • Discretionary access control. Each object within the system, for example files, printers and processes, must have an owner—who can grant or restrict access to the resources at various degrees of granularity.
  • Auditing Capabilities. The system must provide the ability to log all user actions and object access, and include enough information to identify the user that performed any operation. Such information must only be accessible by system administrators.
  • Safe Object reuse. The system must guarantee that any discarded or deleted object cannot be accessed, either accidentally or deliberately, by other entities.
  • System integrity. The system must protect resources belonging to one entity, from being interfered with by another entity.

The C2 guidelines are applicable to standalone systems, and are specified in the document Trusted Computer System Evaluation Criteria (TCSEC). Fortunately, to make life simpler, this is often referred to as the Orange Book, thanks to the color of its cover. Other specifications that expand on the Orange Book include the Red Book for networking, and the Blue Book for subsystems.

Obtaining C2 certification is a long and complex task, and Microsoft are pushing hard for complete certification. Windows NT has passed the Orange Book certification process (for a standalone PC, not connected to a network) and is on the DOD’s official list of evaluated products. At the time of writing, Windows NT 4.0 is undergoing Red and Blue book evaluations.

Read More…Windows NT Security Systems