深圳机场对外门户解决方案.pptVIP

Instructor Notes This is the first step for the SharePoint admin after the identity store is in place. Instructor Notes Point out here that the slide is showing the OOB default SQL Server provider ASP.NET gives us. The role manager is optional. Instructor Notes SharePoint Central Administration will make the changes in teh web.config for you. Instructor Notes Another task is defining what an anonymous user will be able to do. Instructor Notes And next, administrators can point one or more accounts (stored in our own custom identity store) as admins for the site. Stress here that the people picker is now allowing you to work with this custom accounts because SharePoint Central Admin knows that the authentication provider for the Web application has been changed from Windows Authentication to Forms Authentication Instructor Notes This will be the result. For the site it does not really matter anymore whether the user is authenticated as a Windows account or as a custom account. Instructor Notes At the site level, an administrator can decide what the anonymous users will be able to access. Instructor Notes The lucky guy who gets in first is responsible for inviting the others and associating a set of permissisons. Instructor Demo Using SharePoint Central Administration, create and extend an IIS Web Application Use NTML as the security Turn on anonymous access Create a site collection with the top level site being an Internet Presence Web site Show the OOB template – do not cover the different sites and pages yet Point out that now we are authenticated using Windows accounts Use the ASP.NET Web Administration Application (available from a VS.NET 2005 project) to create some accounts in the ASPNETDB database in SQL Server 2005 Go back to SharePoint Central Administration and change the authentication provider from Windows to Forms type in the ASP.NET SQL Membership provider Refresh the internet site and the logon page will be displayed. Open the web.config