LUSH-PEDIA

I> Create or Convert existing web applications to use Claims Based Authentication II> Create User IDs in SQL Database III> Modify web.config file IV> Give Permissions to users present in SQL database Create or Convert existing web applications to use Claims Based Authentication Note: -  Web Application has to be created from the Central Administration console or PowerShell, however it should be using  Claims Based Authentication . A. Creating web application using Central administration Open Central Administration Console. Click on Manage Web application Under Application Management. Click on new on the Ribbon. Chose Claims based Authentication From the top of the page. Choose the port no for the web application. Click on  Enable Forms Based Authentication (FBA)  Under Claims Authentication Types. Windows Authentication is enabled by default and if you dont need windows authentication then you need to remove the check...

$App = get-spwebapplication “URL” $app.useclaimsauthentication = “True” $app.Update() Example:- $App = get-spwebapplication “http://sp1:8000” $app.useclaimsauthentication = “True” $app.Update()

Solution 1 :    web.config <PeoplePickerWildcards>       <clear />       <add key="fbaMembers" value="%" />      <!--added by umair-->       <add key="AspNetSqlMembershipProvider" value="%" /> </PeoplePickerWildcards> Solution 2: web.config <PeoplePickerWildcards>       <clear />       <add key="membership provider" value="%" />       <add key="role provider" value="%" />       <add key="AspNetSqlMembershipProvider" value="%" /> </PeoplePickerWildcards> Solution 3: Set db_owner permissions for AppPool account in provider database.

Add Solution Add-SPSolution c:\solutions\myproject.wsp Install-SPSolution –Identity myproject.wsp –WebApplication http://myprojectsite -GACDeployment Note: You can also use the following parameters –CASPolicies: If you are not deploying to the GAC –AllWebApplications: if you want to deploy the solution to all web applications –Force: to force the deployment of the solution Update-SPSolution –Identity myproject.wsp –LiteralPath c:\solutions\myproject.wsp –GACDeployment Uninstall-SPSolution –Identity myproject.wsp –WebApplication http://myprojectsite Remove-SPSolution –Identity myproject.wsp Enable-SPFeature –Identity MyFeature –url http://myprojectsite Disable-SPFeature –Identity MyFeature –url http://myprojectsite

Create the project In Visual Studio 2010, create a new "Empty SharePoint Project" and name it "MyAnonymousWebPages". Click OK Enter your SharePoint site Select "Deploy as a farm solution" Adding the custom Pages Next, we need to map the 'layouts' directory to our project, so our files are deployed there. Right click on the project name 'MyAnonymousWebPages' > Add > SharePoint "Layouts" Mapped Folder SharePoint will automatically add a folder under 'layouts' with the name of our project. Right click on this folder >Add > New Item > Application Page Name the page "HelloWorld.aspx" Your project should now look like this: Allowing anonymous access So far, we haven't done anything special. The steps we've taken is the basic approach to adding custom application pages. In the following steps, we will inherit from "UnsecuredLayoutsPageBase". This is a base class for...

Error : "Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid." Resolution : http://technet.microsoft.com/en-us/LIBRARY/ff607221(v=exchg.80)   Configure Kerberos Authentication Start Internet Information Services (IIS) Manager. In the Connections pane, expand Default Web Site, and then click PowerShell. In the /PowerShell all authentications should be disable. In the /PowerShell Home pane, double-click Modules. Confirm that Kerbauth is a native module. Confirm that the path of the Kerbauth.dll file is C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. Verify that the Kerbauth module is registered but not enabled on the default Web site. To do this, follow these steps: Click the default Web site in the Connections pane, and then double-click...