Url- http://sharepointa2z.blogspot.in/2009/05/sharepoint-interview-question-part-3.html

Authentication Model in SharePoint?

1. Window

In Windows Based Authentication ASP.NET Relies on IIS to authenticate Incoming request using one of its available Authenticate Methods.

a) Basic Authentication:-Basic Authentication is Compatible with most browsers. But Password is sent in Clear Text. These are Protected with SSL Encryption.

b) Digest Authentication:- Digest Authentication is introduced with HTTP 1.1,So it may not support all browsers. It sends hashed value instead of Clear-Text Password, its more secure than Basic Authentication. But it requires a Windows 2000 Domain Controller.

c) Integrated windows (NTLM)[NT LAN Manager] Authentication:-Integrated Windows Authentication is Available only with Internet Explorer. Its most secure method because it never sends a username /Password over the network., but it will not work over HTTP Proxy Connection.

2. Form Level

Form-Based Authentication allows developers to easily implement “roll-your-own” security in their Applications. All you need to do is create the login page, tell ASP.NET where to find (via web.config) and set the desired Authorisation restrictions. In your login page, you can verify username and password credentials entered by user against a database, windows 2000 autrhenticate directory.Once Credentials are verified you can use methods exposed by Forms Authentication class to set or remove an authentication cookie redirect the user to original page they requested or renew the authentication Cookie.

3. Passport

Password Authentication used the Centralized Password service provided by Microsoft. Passport authentication gives users a single login to use with any passport-enabled site.

In order to use Passport Authentication with ASP.NET , you must download and install SDK, which is available with www.passport.com/business

4. None[Annonyames]

Difference between a Site Definition and a Site Template?

Site Definitions are stored on the hard drive of the SharePoint front end servers. They are

used by the SharePoint application to generate the sites users can create. Site Templates are created by users as a copy of a site they have configured and modified so that they do not have to recreate lists, libraries, views and columns every time they need a new instance of a site.

Sandbox Limitations

1-No Security Elevation

2-No Email Support

3-No Support to WebPartPages Namespace - Microsoft.SharePoint.WebPartPages namespace.

4-No Support to external Webservice

5-No GAC Deployment - Sandbox solutions are not stored in File System(Physical path) and assemblies can't be deployed to Global Assembly Cache(GAC). But it's available on

C:\ProgramData\Microsoft\SharePoint\UCCache at runtime. Note the ProgramData is a hidden folder.

6-No Visual Webparts

Difference Between .dwp and .webpart

1..dwp was the file extension used in version 2 of SharePoint and .webpart is a new extension used in version 3

2.version number on the xmlns attribute is different[2->2003, 3-> 2007]

3.The main difference is that all properties passed to the web part are specified with a

property element and a name attribute in version 3. Version 2 uses different element names for everything.

Web Part Life Cycle :-

OnInit- to configure the webpart.

OnLoad- to load add controls.

CreateChildControls- It is use to create controls and set its property.

LoadViewState- The view state of the web part is populated over here.

OnPreRender- it is use to change the web part properties.

RenterContents- it generate the output in html.

OnUnLoad- to unload the web part.

Dispose- to free the memory.

WebPart life cycle in sharepoint….

On Page Load:

1-Constructor

2-OnInit: Configuration values set using WebBrowsable properties and those in web part task pane are loaded into the web part. In this method we define controls that will be involved with WebPart.

3-OnLoad

4-ConnectionProvider method is called if web part is connectable and returns the connection provider interface object

5-ConnectionConsumer method is called if web part is connectable and sets the connection provider interface in the webpart(Consumer Webpart)

6-CreateChildControls: In this method we define control properties and methods previously declared. All the controls specified are created and added to

7-controls collection. EnsureChildControls() checks to see if the CreateChildControls method has yet been called, and if it has not, calls it.

8-User Generated Event: eg. button click on the web part.

9-OnPreRender :Here we can change any of the web part properties before the control output is drawn (if your web part is connectable you would call the 10-connection provider(method present in the provider webpart eg: GetRowData()) here to retrieve data)

11-SaveViewState: View state of the web part is serialized and saved.

12-Render: Html Output is generated

13-RenderChildren

14-RenderContents

On 1st Postback

1-Constructor

2-OnInit

3-CreateChildControls (If the webpart is Consumer webpart this method is called after the ConnectionConsumer method(6th stage) )

4-OnLoad

5-ConnectionProvider method is called if web part is connectable and returns the connection provider interface object

6-ConnectionConsumer method is called if web part is connectable and sets the connection provider interface in the webpart(Consumer Webpart)

7-User Generated Event

8-PostBack click handling

9-OnPreRender (if your web part is connectable you would call the connection provider(method present in the provider webpart eg: GetRowData()) here to retrieve data)

10-SaveViewState

11-Render

12-RenderChildren

13-RenderContents

On 2nd Postback

1-Constructor

2-OnInit

3-LoadViewState: The view state of the web part is populated over here.

4-CreateChildControls CreateChildControls (If the webpart is Consumer webpart this method is called after the ConnectionConsumer method(7th stage) )

5-OnLoad

6-ConnectionProvider method is called if web part is connectable and returns the connection provider interface object

7-ConnectionConsumer method is called if web part is connectable and sets the connection provider interface in the webpart(Consumer Webpart)

8-User Generated Event

9-PostBack click handling

10-OnPreRender (if your web part is connectable you would call the connection provider(method present in the provider webpart eg: GetRowData()) here to retrieve data)

11-SaveViewState

12-Render

13-RenderChildren

14-RenderContents