Abblix.OIDC.Server.SharedSignals
3.0.0
Prefix Reserved
dotnet add package Abblix.OIDC.Server.SharedSignals --version 3.0.0
NuGet\Install-Package Abblix.OIDC.Server.SharedSignals -Version 3.0.0
<PackageReference Include="Abblix.OIDC.Server.SharedSignals" Version="3.0.0" />
<PackageVersion Include="Abblix.OIDC.Server.SharedSignals" Version="3.0.0" />
<PackageReference Include="Abblix.OIDC.Server.SharedSignals" />
paket add Abblix.OIDC.Server.SharedSignals --version 3.0.0
#r "nuget: Abblix.OIDC.Server.SharedSignals, 3.0.0"
#:package Abblix.OIDC.Server.SharedSignals@3.0.0
#addin nuget:?package=Abblix.OIDC.Server.SharedSignals&version=3.0.0
#tool nuget:?package=Abblix.OIDC.Server.SharedSignals&version=3.0.0
Abblix.OIDC.Server.SharedSignals
Runs an Abblix Shared Signals transmitter on an Abblix OIDC Server, so that each tenant transmits as itself.
Each tenant of the server is an issuer of its own, and a transmitter answering for all of them alike would let one tenant's receivers see another's streams and receive events signed in the name of the wrong issuer. This package keeps them apart:
- each tenant's streams, queued events and delivery claims are kept apart from the others' in whatever stores the transmitter uses, so two tenants may declare a stream under the same receiver and stream identifiers;
- the issuer, the key set address and the endpoint addresses a tenant's receivers see are that tenant's, and follow it when the server's tenant catalog moves it to another issuer;
- every security event token is signed with the keys of the tenant it is transmitted for;
- push delivery runs for each tenant the server serves, in turn;
- once a running instance releases a tenant, at least one refresh period after the tenant left the store of tenants, its streams and the events queued on them are deleted, and a stream that cannot be deleted is logged. A tenant that left the store while no instance served it, as during a restart, is not released by the instances that start afterwards, so its streams stay.
Install
dotnet add package Abblix.OIDC.Server.SharedSignals
dotnet add package Abblix.OIDC.Server.MinimalAPI
The examples below map the server with the Minimal API package; an MVC host installs Abblix.OIDC.Server.MVC instead.
Turning it on
Register the transmitter and the stores it uses first, then the server and the transmitter's part in it:
using Abblix.Jwt;
using Abblix.Oidc.Server.AspNetCore.MultiTenancy;
using Abblix.Oidc.Server.Features.Consents;
using Abblix.Oidc.Server.Features.MultiTenancy;
using Abblix.Oidc.Server.MinimalApi;
using Abblix.Oidc.Server.SharedSignals;
using Abblix.SecurityEvents.Infrastructure;
using Abblix.SharedSignals.Infrastructure;
using Abblix.SharedSignals.Transmitter;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddSecurityEvents();
builder.Services.AddSharedSignalsTransmitter(new SharedSignalsTransmitterOptions
{
Issuer = "https://idp.example.com",
JwksUri = new Uri("https://idp.example.com/.well-known/jwks"),
EventsSupported = ["https://schemas.openid.net/secevent/caep/event-type/session-revoked"],
});
// Grants every client everything it asks for, which suits only clients of your own;
// to ask the end user for consent, register your own IUserConsentsProvider instead
builder.Services.AddConsentGrantedForEveryClient();
builder.Services
.AddOidcServices(options => options.Tenants.Add(new TenantDefinition
{
Id = "acme",
Issuer = new Uri("https://idp.example.com/acme"),
SigningKeys = [JsonWebKeyFactory.CreateRsa(PublicKeyUsages.Signature, SigningAlgorithms.RS256)],
}))
.AddSharedSignals();
The transmitter's issuer names the host without a path. Each tenant's addresses take their paths from the options and put them under the tenant's issuer: for a tenant whose issuer is https://idp.example.com/acme, the configuration document is served at https://idp.example.com/.well-known/ssf-configuration/acme and its key set address is https://idp.example.com/acme/.well-known/jwks.
Each tenant has a transmitter of its own, and what your code resolves from the container - the event dispatcher, the stream store, the event outbox, the stream management service - is the part of the transmitter of the tenant served when it is resolved. Resolve it in the request of the tenant the event belongs to, or inside TenantScope.Enter for that tenant. Until the tenant is released, a part that reaches its streams, queued events or signing keys refuses to, once it is used where its tenant is not served, so a part kept across requests by mistake fails rather than putting one tenant's events on another's streams or signing them with another's keys.
A tenant signs its events with its first signing key that performs an algorithm SecurityEventsOptions.AllowedSigningAlgorithms allows, RS256 when you set nothing. A tenant held to a FAPI profile signs only with PS256 or ES256: FAPI 1.0 Part 2 section 8.6 requires one of them, and FAPI 2.0 section 5.4.1 adds EdDSA, which this library does not implement. When you set nothing, such a tenant signs with PS256 or ES256 rather than RS256, while what the receiver side of the same host accepts stays RS256; a list you set is narrowed to those two. Give the tenant a key that performs one of them; a key declaring no algorithm, as one taken from a certificate, signs with the first its material performs. A tenant whose own keys perform none of them is refused as every tenant with a key it cannot use is: the server does not start with it in its settings, and a tenant store's reading leaves it out. Keys a custodian holds are not judged at startup, and with none that qualifies the tenant's events wait in the outbox; with a key provider of your own, the keys listed in the tenant's settings are the ones judged.
A tenant catalog of your own hands every request the tenant's definition in force, and so does your code to every tenant scope it enters: the transmitter answers and signs as the definition it was last served at, so a stale one brings back the keys and the issuer it names. Each push delivery pass serves every tenant the definition your catalog answers with at that moment, so pushed events follow a move or a key change without waiting for a request, and a tenant your catalog no longer serves is pushed nothing. When your catalog moves a tenant to another issuer, the streams the tenant declares are answered with the new issuer and a poll address under it, while their stored records keep what they were first written with until the server restarts.
With the Redis stream store, each tenant's streams are kept on a hash of the tenant's own, so each event dispatched and each tenant's push delivery pass reads that tenant's streams alone. A store you wrap around it implements IPartitionedStreamStore and returns the inner store's partition wrapped, or the server does not start.
A request that reaches no tenant is answered 404. A receiver is accepted only with credentials the tenant's own issuer issued: the issuer is read from the iss claim the host's authentication leaves behind, or through ReceiverIssuerSelector of SharedSignalsEndpointOptions where the host keeps it elsewhere. So a receiver of one tenant cannot reach another tenant's streams by presenting its credentials under that tenant's address, even with the same identifier.
A tenant can declare its streams in configuration instead of letting its receivers create them. The declared streams are that tenant's stream set, and only its receivers find them:
using Abblix.Oidc.Server.Features.MultiTenancy;
using Abblix.Oidc.Server.MinimalApi;
using Abblix.Oidc.Server.SharedSignals;
using Abblix.SharedSignals.Transmitter;
builder.Services
.AddOidcServices(options => options.Tenants.Add(acme))
.AddSharedSignals()
.AddConfiguredStreams("acme", builder.Configuration.GetSection("Acme:Streams").Get<ConfiguredStream[]>() ?? []);
The server does not start when the stream store, the event outbox, the transmitter's identity or its delivery pass has been replaced after AddSharedSignals(), when the transmitter's issuer names a path or its key set address is on another host, or when streams are declared for the whole server with AddSharedSignalsConfiguredStreams, since those belong to no tenant's receivers.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net11.0 is compatible. |
-
net11.0
- Abblix.OIDC.Server (>= 3.0.0)
- Abblix.SharedSignals (>= 3.0.0)
- Google.Protobuf (>= 3.36.2)
- Microsoft.Extensions.Caching.Memory (>= 11.0.0)
- Microsoft.Extensions.Configuration (>= 11.0.0)
- Microsoft.Extensions.Configuration.Binder (>= 11.0.0)
- Microsoft.Extensions.DependencyInjection (>= 11.0.0)
- Microsoft.Extensions.Http (>= 11.0.0)
- Microsoft.Extensions.Logging (>= 11.0.0)
- System.Threading.RateLimiting (>= 11.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 3.0.0 | 48 | 11/18/2026 |
Runs a Shared Signals transmitter per tenant on a multi-tenant server. Full details: https://github.com/Abblix/Oidc.Server/releases/tag/v3.0