Microsoft Office Tutorials and References
In Depth Information
The settings in the Authentication section are new to this version of SharePoint. Microsoft
is trying to be more flexible with SharePoint’s authentication capabilities, offering either the
old-fashioned Windows authentication classic mode or claims-based authentication. Classic
mode authentication doesn’t take advantage of any of the new claims-based, token-passing
features of Microsoft’s Windows Identity Foundation (WIF) technologies. It works exactly
like the perfectly functional mode used by the previous versions of SharePoint, with the
exception of forms-based authentication. With this version of SharePoint, if you want to do
FBA, the web application has to be set to claims-based authentication.
Claims-based authentication uses the new Windows Identity Foundation technologies
and supports more than one authentication type per zone; it also handles alternate forms
of authentication, such as forms-based, better.
2. For our uses, the classic authentication mode (the default) is fine, so keep it selected.
The next section, IIS Web Site, contains the settings particular to IIS and critically
important to how users will access the site. The settings here are directly passed to IIS when the
web application is created.
3. You have the option in the IIS Web Site section to either use an existing IIS Web Site or
create a new one. In this case we are going to create a new one. That option is selected by
default, so keep it.
If you had created an empty IIS Web Site and wanted to use it for your new SharePoint web
application, you could specify it here. However, because the mechanism that causes SharePoint to propagate
changes to the rest of the servers in the farm is triggered by creating a new website, you would have
to go to each SharePoint server on the farm before creating the web application and manually add
it there before you create the new web application. The new website you create here will be added
to all the SharePoint servers on the farm as a matter of course.
4. Beneath the Create A New IIS Web Site radio button is the field where you can name
the Web Site object. This will be displayed both in IIS and in SharePoint. Currently, the
default SharePoint-80 is listed. That name is actually fine, so we’ll keep it for simplicity’s
sake. However, you can name it anything you like, in case, for example, you need to
comply with company policy.
The next two settings, Port and Host Header, have to do with Web Site addressing. You
basically get two options; either use the server’s name and a unique port number to
access the sites in the web application or apply a host header.
5. As this is the first web application to really host SharePoint sites on the server, it might as
well use the default port 80 to respond to HTTP requests, as well as the server name for the
address. So keep the default. In the future, you can always use alternate access mapping or
extend the web application if you want to use a different address to access the web
application’s content. But this does mean that all other web applications on this server will need to
use either a different port or a host header for its address. This means that the address for
Search JabSto ::

Custom Search