To do this, you must perform the following configurations: 1. Enable the LdapUsers provider.
a. Click AdministrationSettings. The Basic Settings page appears. b. Click Advanced link.
The Settings page appears.
c. In the left pane, click SecurityMembership ProvidersLdapUsers. The properties of LdapUsers appear in the right.
d. Select Enabled checkbox. 2. Edit the LDAP Connection settings.
a. On Settings page, click SecurityLDAP SettingsLDAP ConnectionsDefaultLdapConnection. b. The properties of DefaultLdapConnection appear in the right.
c. Enter the following values:
Field Value
Name DefaultLdapConnection
ServerName <your server name>
For example, enter telerik.com
Port 389
This is the default port, if you use another port to connect to your LDAP provider, you must enter it.
ConnectionDomain <your connection domain> For example, enter telerik
ConnectionUsername Enter the username, which you will use for active directory authentication. ConnectionPassword Enter the password, which you will use for active directory authentication.
UseSsl Leave unselected
ResultCacheExpirationTime 0
MaxReturnedUsers 200
You can change the value if required.
UserDns Filter the users who are going to use Sitefinity.
For example, enter OU=Sitefinity,OU=BG,DC=telerik,DC=com The fields have the following meaning:
DN: distinguished name, DC: domain component, OU: organizational unit, CN: common name.
UserFilter Use this filter for querying AD for users. Use the filter to check if an AD object is a user. For example, enter (&(objectClass=user)(!(objectClass=computer)))
MaxReturnedRoles 200
You can change the value if required.
RolesDNs Filter the roles which are going to use Sitefinity.
For example, enter OU=Sitefinity,OU=BG,DC=telerik,DC=com The fields have the following meaning:
DN: distinguished name, DC: domain component, OU: organizational unit, CN: common name.
RolesFilter Use this filter for querying AD for groups. Use the filter to check if an AD object is a group.
For example, enter (objectClass=group) ConnectWithLogOnCredentials Leave unselected
AuthenticationType Basic
3. Register a new membership provider with the same name as your domain. a. On Settings page, click SecurityMembership Providers.
b. Click Create New button. c. Enter the following values:
Field Value
Name <your domain name>
The value of this field must be the same as ConnectionDomain that you entered in Step 2c.
For example, enter telerik
ProviderType Enter Telerik.Sitefinity.Security.Ldap.LdapMembershipProvider
Enabled Select
4. Restart your web server. 5. Login to Sitefinity backend. 6. Click AdministrationUsers.
7. Click the user to whom you want to give backend access. The Edit user page appears.
8. Select This user can access site backend checkbox. You can also assign roles to the user by selecting them.
9. Open the web.config file that is located in your project’s folder.
10. Find <configuration><system.web> and under it insert <authentication mode="Windows"/>. 11. Save and close the web.config file.
12. Using Internet Explorer 7+, in the address field, enter directly the URL of the page you want to access. For example, enter http://localhost:4000/Sitefinity/Default.aspx.
The system takes you directly to the Dashboard.
NOTE: If you are running Sitefinity locally, open the project manager, select your project and click Edit in Visual Studio. In the Solution Explorer, click Properties. In the left pane, click Web tab. Under Servers, select NTLM Authentication.
| System settings | Table of contents |
CONFIGURING CACHING
Libraries, such as image albums or video libraries, support output (server) and client (browser) caching. Configuring caching increases your performance.
Output and client caching are controlled with cache profiles, which you can configure in the following way: 1. Click AdministrationSettings.
The Basic Settings page appears. 2. Click Advanced link.
The Settings page appears.
The following globally available caching profiles appear: Type of caching Available profiles
Output Cache Profiles No caching
The output caching is disabled for this profile. Output will not be cached. Standard caching
This is the default profile for all content. It is set to expire in 120 seconds and SlidingExpiration is enabled.
Long caching
It is set to expire in 1 200 seconds, absolute time. Client Cache Profiles No caching
The client caching is disabled. No expiration of the content will be set and the actuality will be verified for every page request.
Standard caching
This is the default profile for all content. It is set to expire in 90 days from the request. Long caching
It is set to expire in 1 year from the request. These profiles are applicable to page and content caching.
You can set cache profiles to individual pages or libraries. If no profile is set to a page or library, the default profile is applied. You can change the default profiles and you can globally turn on and off output and client caching, regardless of individual settings made on pages and libraries.
| System settings | Table of contents |
DEPLOYMENT
You use the following deployment procedures to migrate a Sitefinity project from your development machine to a production server. After the physical relocation of the application, all CMS functionality continues to operate. You do not need to install Sitefinity on the server. You must only move the files of the project to the production server.
IMPORTANT: To successfully deploy Sitefinity, your hosting provider must support .NET 4.0 Framework and Full trust. You can find a list of Sitefinity’s official hosting partners on http://www.sitefinity.com/partners/hosting-partners.aspx.
The following screenshot is an example of your project files:
The files are located in your Projects folder.
For more information about managing your project files, see File management. Section contents
Deploy projects to shared hosting
Use this procedure to migrate an existing Sitefinity project from your development machine to a shared hosting using an FTP connection.
Deploy projects to a private virtual server
Use this procedure to migrate an existing Sitefinity project to a virtual server to which you have full access. Deploy Sitefinity projects to Windows Azure
Use this procedure to migrate your Sitefinity project to Windows Azure cloud services. | Table of contents |