Page History
...
.NET Runtime configuration
TODO
...
The .NET Runtime reads the authentication configuration from Web.config using the ASP.NET standard mechanisms for membership and role services. Blueriq has a DefaultMembershipProvider and DefaultRoleProvider that will read its users and roles from Web.config sections.
Example of using the Blueriq providers:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="defaultMembership" type="Aquima.WebApplication.Foundation.Security.DefaultMembershipProviderHandler" />
<section name="defaultRoleProvider" type="Aquima.WebApplication.Foundation.Security.DefaultRoleProviderHandler" />
...
</configSections>
<defaultMembership>
<users>
<user name="admin" password="welcome" />
<user name="user" password="welcome" />
</users>
</defaultMembership>
<defaultRoleProvider>
<users>
<user name="admin">
<roles>
<role name="admin" />
</roles>
</user>
</users>
</defaultRoleProvider>
<system.web>
<authentication mode="Forms" />
<membership defaultProvider="defaultProvider">
<providers>
<add name="defaultProvider" type="Aquima.WebApplication.Foundation.Security.DefaultMembershipProvider" />
</providers>
</membership>
<roleManager enabled="true" defaultProvider="defaultProvider">
<providers>
<add name="defaultProvider" type="Aquima.WebApplication.Foundation.Security.DefaultRoleProvider" />
</providers>
</roleManager>
...
</system.web>
...
</configuration> |
It is also possible to configure ASP.NET built-in providers (for example ActiveDirectoryMembershipProvider and/or AuthorizationStoreRoleProvider) or create your own implementations of System.Web.Security.MembershipProvider and/or System.Web.Security.RoleProvider.
...
Overview
Content Tools