Corely.IAM.Web
9.0.0
See the version list below for details.
dotnet add package Corely.IAM.Web --version 9.0.0
NuGet\Install-Package Corely.IAM.Web -Version 9.0.0
<PackageReference Include="Corely.IAM.Web" Version="9.0.0" />
<PackageVersion Include="Corely.IAM.Web" Version="9.0.0" />
<PackageReference Include="Corely.IAM.Web" />
paket add Corely.IAM.Web --version 9.0.0
#r "nuget: Corely.IAM.Web, 9.0.0"
#:package Corely.IAM.Web@9.0.0
#addin nuget:?package=Corely.IAM.Web&version=9.0.0
#tool nuget:?package=Corely.IAM.Web&version=9.0.0
Corely.IAM.Web
Reusable Razor Class Library (RCL) that provides the Blazor Server UI for the Corely.IAM identity and access management library: authentication pages, and management components the host places at its own paths.
Upgrading from 6.x? See MIGRATION-IAM.Web-7.0.md. The package ships components only: the host writes a page per component and supplies every link.
What the library provides
- Management components: account, users, groups, roles, permissions, audit, profile, invitations and platform settings, each placed by the host in a short page shell
- Razor Pages: Sign In, Register, Sign Out, Select Account, Switch Account, Create Account
- Shared components: Alert, Pagination, ConfirmModal, FormModal, EntityPickerModal, EffectivePermissionsPanel, PermissionView, LoadingSpinner, and more
- Middleware: correlation ID, JWT cookie → UserContext. Security headers are the host's; see Security
- Authentication: cookie-based auth wired to Corely.IAM's JWT token system
- Static assets:
iam-web.css(custom styles),modal-keyboard.js - Account route guard:
AccountScope, so a host can put the account in its paths - Route constants:
AppRoutesnames the authentication endpoints, the only fixed paths
What the host is responsible for
SecurityConfigurationProvider: reads the system encryption key from config and implementsISecurityConfigurationProvider. The library defines the interface; the host provides the implementation.- Database / EF configuration: choosing and wiring the EF provider (SQL Server, MySQL)
- Blazor host shell:
App.razor,Routes.razor,Program.cs, its layout and navigation - Page shells and links: a page per component at the host's paths, and an
IIamWebLinkssaying where each lives (Hosting Pages) - Static asset references: Bootstrap, Bootstrap Icons (must be served by the host)
- Logging: Serilog or any other provider of your choice
Integration steps
1. Add a project reference
<ProjectReference Include="..\Corely.IAM.Web\Corely.IAM.Web.csproj" />
2. Implement SecurityConfigurationProvider
The host must provide an implementation of ISecurityConfigurationProvider that returns the system symmetric key. Create this in your host project. The library intentionally does not provide it, so the host controls how the key is sourced (config, key vault, environment variable, etc.).
// YourHost/Security/SecurityConfigurationProvider.cs
using Corely.IAM.Security.Providers;
using Corely.Security.KeyStore;
internal class SecurityConfigurationProvider(IConfiguration configuration)
: ISecurityConfigurationProvider
{
private readonly InMemorySymmetricKeyStoreProvider _keyStoreProvider = new(
configuration["Security:SystemKey"]
?? throw new InvalidOperationException("Security:SystemKey not found in configuration")
);
public ISymmetricKeyStoreProvider GetSystemSymmetricKey() => _keyStoreProvider;
}
3. Register services in Program.cs
using Corely.IAM.Web.Extensions;
// Razor Pages + cookie auth + shared services
builder.Services.AddRazorComponents().AddInteractiveServerComponents();
builder.Services.AddSingleton(TimeProvider.System);
builder.Services.AddIAMWeb(); // Razor Pages, auth, cookie manager
builder.Services.AddIAMWebBlazor<MyIamLinks>(); // Blazor auth state, the host's IIamWebLinks
// Instantiate your SecurityConfigurationProvider and wire up IAM core services
var securityConfigProvider = new SecurityConfigurationProvider(builder.Configuration);
builder.Services.AddIAMServicesWithEF(builder.Configuration, securityConfigProvider, efConfig);
AddIAMWeb() registers:
IAuthCookieManager: reads/writes the auth JWT cookieIUserContextClaimsBuilder: convertsUserContexttoClaimsPrincipal- Cookie authentication scheme (login path
/signin, logout path/signout) - Authorization services
AddIAMWebBlazor<TLinks>() registers:
IBlazorUserContextAccessor: access the current user context from Blazor componentsAuthenticationStateProvider: Blazor auth state backed by the cookieIAccountDisplayState: reactive state for displaying the current account name in the navbar- Cascading authentication state
IIamWebLinks: the host'sTLinks
4. Set up the middleware pipeline
Order matters. Call UseIAMWebAuthentication() before the endpoints are mapped. MapStaticAssets()
with WithStaticAssets() fingerprints IAM.Web's CSS and scripts, so a browser never keeps an old
copy after an upgrade:
using Corely.IAM.Web.Extensions;
app.UseIAMWebAuthentication(); // correlation ID → JWT validation → auth/authz
app.UseHttpsRedirection();
app.UseAntiforgery();
app.MapStaticAssets();
app.MapRazorPages().WithStaticAssets();
app.MapRazorComponents<App>()
.WithStaticAssets()
.AddInteractiveServerRenderMode();
UseIAMWebAuthentication() applies middleware in this order:
CorrelationIdMiddleware: assigns a correlation ID to every requestAuthenticationTokenMiddleware: validates the JWT auth cookie and populatesUserContextUseAuthentication(): ASP.NET Core authenticationUseAuthorization(): ASP.NET Core authorization
It sets no security headers. Set them in the host, before this call; Security has a starting set.
5. Write the page shells and the router (Routes.razor)
The library has no routed Blazor pages, so the router routes only the host's assembly. Each page is a short shell around a component, at a path the host chooses:
@page "/accounts/{AccountId:guid}/users"
@rendermode @(new InteractiveServerRenderMode(prerender: false))
<PageTitle>Users</PageTitle>
<AccountScope AccountId="AccountId">
<UserList />
</AccountScope>
@code {
[Parameter] public Guid AccountId { get; set; }
}
<Router AppAssembly="typeof(Routes).Assembly">
<Found Context="routeData">
<AuthorizeRouteView RouteData="routeData" DefaultLayout="typeof(MainLayout)">
<NotAuthorized>
<Corely.IAM.Web.Components.Shared.RedirectToLogin />
</NotAuthorized>
</AuthorizeRouteView>
</Found>
</Router>
Hosting Pages covers every shell, IIamWebLinks and AccountScope.
Corely.IAM.WebApp has a working shell for every component.
6. Reference static assets in App.razor
The library's CSS is served from the RCL's static asset path. Bootstrap and Bootstrap Icons must also be present (served by the host via libman, npm, or CDN):
<link rel="stylesheet" href="lib/bootstrap/dist/css/bootstrap.min.css" />
<link rel="stylesheet" href="lib/bootstrap-icons/font/bootstrap-icons.min.css" />
<link rel="stylesheet" href="app.css" />
<link rel="stylesheet" href="_content/Corely.IAM.Web/css/iam-web.css" />
<script src="lib/bootstrap/dist/js/bootstrap.bundle.min.js"></script>
<script src="_framework/blazor.web.js"></script>
Required configuration (appsettings.json)
{
"ConnectionStrings": {
"DefaultConnection": "Server=...;Database=CorelyIAM;..."
},
"Database": {
"Provider": "mssql"
},
"Security": {
"SystemKey": "<hex key, generated with Corely.IAM.DevTools: dotnet run -- sym-encrypt --create>"
},
"SecurityOptions": {
"MaxLoginAttempts": 5,
"AuthTokenTtlSeconds": 3600,
"AuthSessionTtlSeconds": 604800
},
"PasswordValidationOptions": {
"MinimumLength": 8,
"RequireUppercase": true,
"RequireLowercase": true,
"RequireDigit": true,
"RequireNonAlphanumeric": true
}
}
| Key | Required | Notes |
|---|---|---|
ConnectionStrings:DefaultConnection |
✅ | Database connection string |
Database:Provider |
✅ | mssql or mysql |
Security:SystemKey |
✅ | Base64 symmetric key, generated with DevTools |
SecurityOptions:* |
✅ | Login lockout, access-token TTL, and renewable session TTL |
PasswordValidationOptions:* |
✅ | Password rules |
Generate a system key with the DevTools project:
cd Corely.IAM.DevTools
dotnet run -- sym-encrypt --create
Fixed routes (AppRoutes)
The authentication endpoints are Razor Pages at fixed routes, named on Corely.IAM.Web.AppRoutes:
SignIn, Register, SignOut, SelectAccount, SwitchAccount, CreateAccount, VerifyMfa,
GoogleCallback, RegisterWithGoogle, Privacy and Terms. Every other path is the host's.
Shared components
Import the library's namespace in your _Imports.razor or reference components fully qualified:
@using Corely.IAM.Web.Components.Shared
| Component | Description |
|---|---|
Alert |
Dismissable alert banner |
ConfirmModal |
Generic confirmation dialog |
FormModal |
Generic form dialog |
EntityPickerModal |
Searchable paginated entity picker |
EffectivePermissionsPanel |
Displays CRUDX badges + role derivation tree. Accepts UseCard parameter (default true) |
PermissionView |
Conditionally renders children based on CRUDX permission check |
Pagination |
Server-side pagination controls |
LoadingSpinner |
Loading indicator |
RedirectToLogin |
Redirects unauthenticated users to /signin, returning to the page afterwards |
AccountScope |
Renders its content only in the account its route names, switching first |
Architecture notes
- The library targets net10.0 and uses Blazor Interactive Server render mode throughout. Pre-rendering is disabled in every shell (
prerender: false). - All management components inherit from base classes in
Components/(EntityDetailPageBase,EntityListPageBase,AuthenticatedPageBase) which handle loading state, error messages, confirmation dialogs, and navigation guards. - The
IBlazorUserContextAccessorservice is the correct way to access the current user context from Blazor components. Do not useIHttpContextAccessordirectly in Blazor components.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Corely.Common (>= 2.0.4)
- Corely.IAM (>= 6.2.0)
- Serilog (>= 4.4.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Corely.IAM.Web:
| Package | Downloads |
|---|---|
|
Corely.Billing.Web.IAM
Corely.IAM for Corely.Billing.Web: each grant action gated by IAM's PermissionView, and the account taken from the signed-in user |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 11.4.2 | 46 | 11/17/2026 |
| 11.4.1 | 50 | 11/17/2026 |
| 11.4.0 | 58 | 11/16/2026 |
| 11.3.0 | 68 | 11/15/2026 |
| 11.2.0 | 129 | 11/9/2026 |
| 11.1.1 | 93 | 11/9/2026 |
| 11.1.0 | 98 | 11/9/2026 |
| 11.0.0 | 146 | 11/8/2026 |
| 10.0.0 | 97 | 11/8/2026 |
| 9.5.1 | 113 | 11/4/2026 |
| 9.5.0 | 100 | 11/4/2026 |
| 9.4.0 | 122 | 11/1/2026 |
| 9.3.0 | 112 | 11/1/2026 |
| 9.2.0 | 107 | 11/1/2026 |
| 9.1.0 | 109 | 10/31/2026 |
| 9.0.0 | 146 | 10/31/2026 |
| 8.1.0 | 133 | 10/27/2026 |
| 8.0.1 | 109 | 10/27/2026 |
| 8.0.0 | 122 | 10/27/2026 |
| 7.0.2 | 115 | 10/24/2026 |