Lds.Application.IpAccess 0.104.0
Lds.Application.IpAccess
Lds is Datalogik LDS' framework for .NET web applications: the parts every one of its applications
would otherwise write again — a shell and components for Blazor pages, the Result an operation
answers with, permissions and who holds them, an audit trail and the store it writes to — shipped as
seven packages that share one version. It prescribes no application architecture: an application keeps
its own structure and takes the parts it wants.
| Package | What it is |
|---|---|
Lds.Application |
The technology-blind core: Result and the failure text that words it, permissions and the current user, granted access, the audit trail and the ports its store implements |
Lds.Application.FormattedText |
The formatted-text sanitiser and its rules, apart from the core on weight |
Lds.Application.IpAccess |
The operations that keep the rules of Lds.IpAccess, Datalogik's IP access package — authorized and recorded in the audit trail, apart from the core on weight |
Lds.Infrastructure.MongoDb |
The MongoDB store for the core's ports: the audit trail and granted access |
Lds.Web.Components |
The Blazor components and their SCSS, with Font Awesome Free and the editors they use |
Lds.Web.Components.Testing |
bUnit/xUnit support for testing pages built on the components |
Lds.Web.IpAccess |
The IP access screens over those operations, apart from the components on weight |
The packages are on Datalogik's feed, https://components.datalogik.dk/v3/index.json, and so is Lds.IpAccess.
This package
The operations a solution's administrators keep IP access with: who may open the application from where,
as Lds.IpAccess enforces it. Lds.IpAccess is Datalogik's own package, on the same feed, and holds the
middleware, the rules and the stores; what it does and the options it takes are in
its README. It decides nothing about who
may change its rules; this package does. Each operation authorizes with a permission the solution supplies,
refuses a change that would turn away its maker's current address, answers with a Result, and records in
the audit trail, as Lds' own operations do.
It is a package of its own, apart from Lds.Application, because Lds.IpAccess and what it downloads
need not travel to every consumer of the core. Its API names no web type, so a business layer calls the
operations as a page does; but Lds.IpAccess references ASP.NET Core's shared framework for its middleware,
and that reference comes along with this package. Lds.Web.IpAccess references it for the screens.
The operations, each a class with ExecuteAsync answering with a Result:
| Operation | What it does | Guarded by | Recorded |
|---|---|---|---|
ReadIpAccessPolicy |
The policy, the restricted paths it keeps addresses for, and the caller's own address, country and verdict | mayAdminister |
No: settings |
SaveIpAccessPolicy |
Saves the policy, unless it would lock its maker out | mayAdminister |
Yes |
ListPersonAddresses |
Everybody's own addresses | mayAdminister |
Yes: discloses them |
SavePersonAddresses |
Saves one person's addresses, unless that would lock its maker out | mayAdminister |
Yes |
RemovePersonAddresses |
Removes them, likewise | mayAdminister |
Yes |
ReadIpLists |
How the downloaded lists are doing | mayAdminister |
No |
CheckIpListsNow |
Downloads the lists now | mayAdminister |
Yes |
ReadAccessLog |
The latest turned-away requests, and the iCloud Private Relay days | mayReadAccessLog |
Yes: discloses who was turned away |
Their failure codes are the constants of IpAccessFailures (IpAccess.WouldLockYouOut, IpAccess.NotAPattern, …).
Lds.Web.IpAccess words them in English and Danish; a solution words one in its failure catalogue only where it
wants other words.
Getting started
// Lds.IpAccess, registered by the solution. The operations read the caller's address from this claim.
builder.Services.AddIpAccess(builder.Configuration, options => options.ClientIpClaimType = "client-ip");
builder.Services.AddIpAccessStoredRules();
builder.Services.AddIpAccessMongoDb(database); // Lds.IpAccess.MongoDb; without a store the rules live in memory
// The operations, with the solution's own permissions and failure code.
builder.Services.AddLdsIpAccess(MyPermissions.ManageIpAccess, MyPermissions.ReadIpAccessLog, MyFailures.NotPermitted);
// After the sign-in is known, before authorization.
app.UseAuthentication();
app.UseIpAccess();
app.UseAuthorization();
The operations also need the current user, the sign-in (AddSignedInPrincipal from Lds.Web.Components) and the
audit trail. Without ClientIpClaimType the caller's address is not known, and a change that could lock somebody out is
refused. Everything a solution supplies, and the decision behind each, is in
Adopting the framework §2.9.
Documentation, issues and changes
The source, the documents and the issues are on GitHub, at datalogiklds/webframework. The repository is private: if you have access, report a fault or ask for a change there; if you don't, ask Datalogik LDS for it.
- Adopting the framework — everything a solution supplies to the packages, with the decision behind each item
- Architecture — how Lds is built and where an application's code meets its types
- Using the components — how a page is put together from the components
- Design manual — what the interface looks like and how it behaves
- Glossary — the words the source and the documents use
- Changelog — what changed in each version, and what a solution has to change to take it
Showing the top 20 packages that depend on Lds.Application.IpAccess.
| Packages | Downloads |
|---|---|
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
24 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
10 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
9 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
6 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
5 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
4 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
3 |
|
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
|
2 |
.NET 10.0
- Lds.Application (>= 0.104.0)
- Lds.IpAccess (>= 0.3.0)
| Version | Downloads | Last updated |
|---|---|---|
| 0.146.0 | 3 | 2026-11-17 |
| 0.145.0 | 1 | 2026-11-17 |
| 0.144.0 | 1 | 2026-11-16 |
| 0.143.1 | 0 | 2026-11-16 |
| 0.143.0 | 1 | 2026-11-16 |
| 0.142.0 | 2 | 2026-11-15 |
| 0.141.1 | 4 | 2026-11-15 |
| 0.141.0 | 1 | 2026-11-15 |
| 0.140.0 | 1 | 2026-11-15 |
| 0.139.1 | 9 | 2026-11-15 |
| 0.139.0 | 1 | 2026-11-15 |
| 0.138.0 | 4 | 2026-11-15 |
| 0.137.0 | 2 | 2026-11-15 |
| 0.136.1 | 1 | 2026-11-15 |
| 0.136.0 | 1 | 2026-11-15 |
| 0.135.0 | 1 | 2026-11-15 |
| 0.134.1 | 5 | 2026-11-15 |
| 0.134.0 | 1 | 2026-11-15 |
| 0.133.0 | 1 | 2026-11-15 |
| 0.132.0 | 0 | 2026-11-15 |
| 0.131.0 | 2 | 2026-11-15 |
| 0.130.0 | 2 | 2026-11-15 |
| 0.129.0 | 2 | 2026-11-14 |
| 0.128.0 | 4 | 2026-11-14 |
| 0.127.0 | 1 | 2026-11-14 |
| 0.126.0 | 2 | 2026-11-14 |
| 0.125.1 | 0 | 2026-11-14 |
| 0.125.0 | 1 | 2026-11-14 |
| 0.124.0 | 2 | 2026-11-14 |
| 0.123.0 | 1 | 2026-11-14 |
| 0.122.0 | 1 | 2026-11-14 |
| 0.121.0 | 10 | 2026-11-12 |
| 0.120.0 | 24 | 2026-11-12 |
| 0.119.0 | 1 | 2026-11-12 |
| 0.118.0 | 1 | 2026-11-12 |
| 0.117.0 | 2 | 2026-11-12 |
| 0.116.0 | 2 | 2026-11-11 |
| 0.115.0 | 4 | 2026-11-11 |
| 0.113.0 | 3 | 2026-11-11 |
| 0.112.0 | 6 | 2026-11-11 |
| 0.111.1 | 2 | 2026-11-10 |
| 0.111.0 | 5 | 2026-11-10 |
| 0.110.0 | 1 | 2026-11-09 |
| 0.109.0 | 2 | 2026-11-09 |
| 0.108.1 | 3 | 2026-11-09 |
| 0.108.0 | 4 | 2026-11-09 |
| 0.107.0 | 4 | 2026-11-09 |
| 0.106.1 | 2 | 2026-11-09 |
| 0.106.0 | 1 | 2026-11-08 |
| 0.105.0 | 1 | 2026-11-08 |
| 0.104.0 | 2 | 2026-11-08 |
| 0.103.0 | 2 | 2026-11-08 |
| 0.102.0 | 1 | 2026-11-08 |
| 0.101.0 | 4 | 2026-11-08 |
| 0.100.0 | 1 | 2026-11-08 |
| 0.99.0 | 1 | 2026-11-08 |
| 0.98.1 | 3 | 2026-11-08 |
| 0.98.0 | 1 | 2026-11-08 |
| 0.97.1 | 1 | 2026-11-08 |
| 0.97.0 | 1 | 2026-11-08 |
| 0.96.0 | 0 | 2026-11-08 |