Verifiabl.Extensions.DependencyInjection
0.4.0
Prefix Reserved
Verifiabl.Issuer.Extensions.DependencyInjection
Additional DetailsRenamed to Verifiabl.Issuer.Extensions.DependencyInjection
dotnet add package Verifiabl.Extensions.DependencyInjection --version 0.4.0
NuGet\Install-Package Verifiabl.Extensions.DependencyInjection -Version 0.4.0
<PackageReference Include="Verifiabl.Extensions.DependencyInjection" Version="0.4.0" />
<PackageVersion Include="Verifiabl.Extensions.DependencyInjection" Version="0.4.0" />
<PackageReference Include="Verifiabl.Extensions.DependencyInjection" />
paket add Verifiabl.Extensions.DependencyInjection --version 0.4.0
#r "nuget: Verifiabl.Extensions.DependencyInjection, 0.4.0"
#:package Verifiabl.Extensions.DependencyInjection@0.4.0
#addin nuget:?package=Verifiabl.Extensions.DependencyInjection&version=0.4.0
#tool nuget:?package=Verifiabl.Extensions.DependencyInjection&version=0.4.0
Verifiabl.Extensions.DependencyInjection
Dependency-injection wiring for the Verifiabl .NET SDK. Registers IVerifiablClient and connects it to IHttpClientFactory, so the core Verifiabl package stays dependency-light.
dotnet add package Verifiabl.Extensions.DependencyInjection
using Microsoft.Extensions.DependencyInjection;
using Verifiabl;
using Verifiabl.Client;
builder.Services.AddVerifiablClient(options =>
{
options.Environment = VerifiablEnvironment.Sandbox;
options.Auth = VerifiablAuth.ClientCredentials(clientId, clientSecret);
});
Then inject IVerifiablClient:
public sealed class PayrollService(IVerifiablClient verifiabl)
{
public Task<RegisterNonPiiResponse> RegisterAsync(RegisterNonPiiRequest request) =>
verifiabl.RegisterNonPiiAsync(request);
}
Use the Action<IServiceProvider, VerifiablClientOptions> overload when the credentials come from another registered service.
The client is registered as a singleton: it caches OAuth access tokens, so a scoped or transient lifetime would fetch a fresh token on every resolve. Its HttpClient comes from the named factory client Verifiabl (VerifiablServiceCollectionExtensions.HttpClientName), which you can further configure with AddHttpClient("Verifiabl"). Setting options.HttpClient yourself takes precedence.
Registration uses TryAdd semantics: the first AddVerifiablClient call wins and later calls are silently ignored, so register the client once at composition-root level rather than from multiple modules.
Full documentation: docs.verifiabl.io.
License
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. 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. |
| .NET Framework | net472 is compatible. net48 was computed. net481 was computed. |
-
.NETFramework 4.7.2
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.2)
- Microsoft.Extensions.Http (>= 8.0.1)
- Verifiabl (>= 0.4.0)
-
net10.0
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.2)
- Microsoft.Extensions.Http (>= 8.0.1)
- Verifiabl (>= 0.4.0)
-
net8.0
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.2)
- Microsoft.Extensions.Http (>= 8.0.1)
- Verifiabl (>= 0.4.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.