LaunchBoxCONTRIBUTORS
On this page

14.1 Beta 1 SDK

This reference documents the current beta SDK. Beta APIs can change before stable.

IPluginCredentialRefreshStore14.1 Beta

C#
public interface Unbroken.LaunchBox.Plugins.Connections.IPluginCredentialRefreshStore : Unbroken.LaunchBox.Plugins.Connections.IPluginCredentialStore
Supports atomic credential snapshots and conditional refresh persistence.

Remarks

Query this optional interface on the injected credential store. Do not fall back to an unconditional save after remote refresh. Providers still coordinate service-side token rotation.

Inheritance and interfaces

Methods

GetSnapshotAsync 14.1 Beta

C#
System.Threading.Tasks.Task<Unbroken.LaunchBox.Plugins.Connections.PluginCredentialSnapshot?> GetSnapshotAsync(string ownerId, string connectionId, System.Threading.CancellationToken cancellationToken)
Reads one descriptor and all its values in the same transaction.
ownerId 14.1 Beta
The package-local owner.
connectionId 14.1 Beta
The owner-local connection handle.
cancellationToken 14.1 Beta
Cancels the read.

Returns

A snapshot containing secrets, or null if the connection no longer exists.

TryUpdateConnectionAsync 14.1 Beta

C#
System.Threading.Tasks.Task<bool> TryUpdateConnectionAsync(Unbroken.LaunchBox.Plugins.Connections.PluginCredentialSnapshot snapshot, Unbroken.LaunchBox.Plugins.Connections.PluginStoredConnection connection, System.Collections.Generic.IReadOnlyDictionary<string, string?> values, System.Threading.CancellationToken cancellationToken)
Updates an existing connection only if its snapshot is still current in this store.
snapshot 14.1 Beta
The snapshot read before remote work.
connection 14.1 Beta
The updated descriptor with the same owner and connection handle.
values 14.1 Beta
Partial value changes, using the same null/removal rules as ordinary saves.
cancellationToken 14.1 Beta
Cancels persistence; completed writes are not rolled back.

Returns

True when accepted, including unchanged values; false when removed or superseded. False makes no changes and publishes no notification.

Remarks

The comparison and write are atomic across participating processes. Discard rejected refresh results; do not continue using their credentials.