Abblix.Utils 2.4.0

Abblix.Utils

The foundation layer of the Abblix packages: the small, dependency-light pieces that security-focused code keeps needing - careful URI construction, log sanitization, cryptographic encodings, JSON converters for wire formats, and a Result type for expected failures. The JWT, OIDC Server, Security Events and Shared Signals packages all build on it; it is equally usable on its own.

Install

dotnet add package Abblix.Utils

What is inside

URIs and parameters

UriBuilder, UriExtensions and ParametersBuilder construct and take apart URIs with explicit control over query and fragment parts - the difference that matters when a redirect URI must carry a response exactly where the protocol says, and nowhere else.

Result: expected failures as values

Result<TSuccess, TFailure> models an operation whose failure is an expected outcome rather than an exception - validation, protocol errors, lookups that legitimately find nothing. Both outcomes are values, Match and the MapSuccess/MapFailure combinators compose them railway-style, and TryGetSuccess/TryGetFailure unwrap at the edges:

Result<AuthorizedGrant, AuthError> result = await AuthorizeAsync(request);
return result.Match(RenderTokens, RenderError);

Log sanitization

Sanitized wraps a value for logging so an ASCII control character cannot forge a log line: at formatting time it escapes line breaks, tabs, quotes and separators, and strips the C0 range and DEL. Wrap anything a caller sent - identifiers, URIs, header values - before it reaches a log template:

logger.LogWarning("Unknown client {ClientId}", Sanitized.Value(clientId));

The stripping runs in ToString(), so it protects the formatted message; a sink that serializes the wrapper's Source property instead reads the raw value by design.

Cryptographic encodings and randomness

CryptoRandom produces cryptographically strong random material for tokens and identifiers. Base32 and HexConverter cover the encodings certificates and secrets travel in, and CertificateId with ICertificateProvider abstracts certificate lookup.

JSON converters for wire formats

Custom System.Text.Json converters for the shapes protocol messages actually use: unix-seconds timestamps (DateTimeOffsetUnixTimeSecondsConverter), durations as integer seconds (TimeSpanSecondsConverter), space-separated lists such as OAuth scopes (SpaceSeparatedValuesConverter), values that arrive as either a single item or an array (SingleOrArrayConverter), base64url binary (Base64UrlTextEncoderConverter), and null-dropping serialization (JsonIgnoreNullsAttribute).

Distributed cache helpers

DistributedCacheExtensions adds the operation IDistributedCache lacks for security bookkeeping: TryAddAsync, an add-if-absent that expresses first-sighting checks - replay caches and similar - over any cache backend. It is Get-then-Set, because the interface exposes no compare-and-set, so the guarantee is probabilistic under concurrency; a domain needing strict exactly-once takes a backend-native atomic (SET NX EX, INSERT ... ON CONFLICT DO NOTHING) instead.

Collections and enums

ArrayExtensions, EnumerableExtensions, EnumFlagExtensions and ObjectExtensions carry the small operations that otherwise get re-implemented per project.

Part of the Abblix product family

Abblix.Utils sits under Abblix.JWT, Abblix.OIDC.Server, Abblix.SecurityEvents and the rest of the family; the full set lives in the repository.

License

Abblix.Utils is licensed under the Apache License 2.0.

Contacts

• General inquiries: info@abblix.com
• Support and security reports: support@abblix.com
• Website: Abblix OIDC Server