At the moment subsystem powers Web application does not require third-party services and comes along with the application in the generation of Flexberry Designer.

The database can be located in the application or in a separate database.

In the configuration file for configuration meets the following unit (Forms authentication):

<!-- Authority system -->
  <unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
    <alias alias="ISecurityService" type="ICSSoft.STORMNET.Security.ISecurityService, ICSSoft.STORMNET.DataObject" />
    <alias alias="CheckingInSessionMode" type="ICSSoft.STORMNET.Security.CheckingInSessionMode, CheckingLibrary" />
    <alias alias="singleton" type="Microsoft.Practices.Unity.ContainerControlledLifetimeManager, Microsoft.Practices.Unity" />
    <container>
      <!-- System configuration authority. -->
      <register type="ISecurityService" mapTo="CheckingInSessionMode">
        <lifetime type="singleton" />
        <constructor>
          <!-- Here it is necessary to register the name of the application -->
          <param name="imprisone" type="System.String" value="WebApp" />
        </constructor>
      </register>      
    </container>
  </unity>

  <authentication mode=Forms >
    <forms name=".ASPXFORMSAUTH" loginUrl="LoginForm.aspx" timeout="30" slidingExpiration="true" />
  </authentication>

  <authorization>
    <deny users="?" />
  </authorization>

  <membership defaultProvider="CaseberryMembershipProvider">
    <providers>
      <clear/>
      <add name="CaseberryMembershipProvider" type="ICSSoft.STORMNET.Security.CaseberryMembershipProvider" applicationName="SLAuthSample"/>
    </providers>
  </membership>

  <roleManager defaultProvider="CaseberryRoleProvider" enabled="true">
    <providers>
      <clear/>
      <add name="CaseberryRoleProvider" type="ICSSoft.STORMNET.Security.CaseberryRoleProvider" />
    </providers>
  </roleManager>

As well as the variant with Windows authentication:

<authentication mode="Windows" />

  <authorization>
    <deny users="?" />
  </authorization>

  <membership defaultProvider="CaseberryDomainMembershipProvider">
    <providers>
      <clear/>
      <add name="CaseberryDomainMembershipProvider" type="CheckingLibrary.Web.CaseberryDomainMembershipProvider, CheckingLibrary" applicationName="SLAuthSample"/>
    </providers>
  </membership>

  <roleManager defaultProvider="CaseberryDomainRoleProvider" enabled="true">
    <providers>
      <clear/>
      <add name="CaseberryDomainRoleProvider" type="CheckingLibrary.CaseberryDomainRoleProvider" applicationName="SLAuthSample" />
    </providers>
  </roleManager>

To use AzMan substitute providers.

Powers can also be configured using the Security Console.

Add users to the database system of authority in windows authentication

Add users to the database system of authority when windows-authentication is described in the appropriate article.

the Creation of powers for classes for Flexberry ASP.NET

The creation of powers for classes for Flexberry ASP.NET described in the appropriate article.

CaseberryDomainRoleProvider

Use CaseberryDomainRoleProvider described in the appropriate article.

CaseberryMembershipProvider

Use CaseberryMembershipProvider described in the appropriate article.

Web forms subsystem powers

The subsystem authorizations for the web-form described in the Web forms subsystem powers.

UserSettingsService

Use UserSettingsService described in the appropriate article.

Переведено сервисом «Яндекс.Переводчик» http://translate.yandex.ru