AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  1. Home
  2. Managing users
  3. User registration and authentication
  4. Configuring forms authentication

Configuring forms authentication


Was this page helpful?

Send us feedback Go back to top
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

With forms authentication, the application stores user names and passwords in the database. Forms authentication is the default option when signing in to the Xperience administration interface.

Configuring forms authentication for multiple web projects

The forms authentication uses standard ASP.NET forms authentication and its settings, which you can find in your application's web.config file:

HTML
<system.web>
 ...
   <authentication mode="Forms">
     <forms loginUrl="CMSPages/logon.aspx" defaultUrl="Default.aspx" name=".ASPXFORMSAUTH" timeout="60000" slidingExpiration="true" />
   </authentication>
 ...
<system.web>

If you are running multiple web projects in virtual directories, and the projects have the same machine key defined, users signing in to one of the applications will be automatically signed in to instances running on other projects. To prevent that, add the path parameter to the above code in each project, as in the following example:

HTML
<authentication mode="Forms">
   <forms loginUrl="CMSPages/logon.aspx" defaultUrl="Default.aspx" name=".ASPXFORMSAUTH" timeout="60000" slidingExpiration="true" path="KenticoXperience" />
</authentication>

Additional configuration options related to user passwords may also be defined in the system, as described in Securing user accounts and passwords.