INotificationDeliveryService Interface

Provides HTTP-based notification services for CIBA ping and push modes.

public interface INotificationDeliveryService

Derived
↳ HttpNotificationDeliveryService

Remarks

This interface supports both CIBA notification modes by sending HTTP POST requests with a notification payload to the client's registered endpoint.

• Ping Mode: Sends auth_req_id to notify client that tokens are ready for retrieval.
• Push Mode: Delivers complete token response directly to client endpoint.

Methods

INotificationDeliveryService.SendAsync(Uri, string, IBackChannelNotificationRequest, string) Method

Sends an HTTP POST notification to the client's registered endpoint.

System.Threading.Tasks.Task<bool> SendAsync(System.Uri clientNotificationEndpoint, string clientNotificationToken, Abblix.Oidc.Server.Features.BackChannelAuthentication.Interfaces.IBackChannelNotificationRequest payload, string mode);

Parameters

clientNotificationEndpoint System.Uri

The HTTPS URL of the client's notification endpoint.

clientNotificationToken System.String

Bearer token for authenticating the notification request.

payload IBackChannelNotificationRequest

The notification payload to send (e.g., ping notification or push token delivery).

mode System.String

The CIBA mode (e.g., "ping" or "push") for logging purposes.

Returns

System.Threading.Tasks.Task<System.Boolean>
true if the client endpoint accepted the notification (2xx response); false if delivery failed (non-success status or transport error).

On false push keeps the stored record, and it is not a resumable delivery. The tokens were minted and are gone; nothing retries them. The record reads Authenticated, written before the mint, so a LATER completion of the same request is refused - the recovery is to ask the end user, not to resend from what is left.