RegistrationRequestSizeValidator Class

Refuses at startup a MaxRegistrationRequestSize that no request could satisfy.

public sealed class RegistrationRequestSizeValidator : Microsoft.Extensions.Options.IValidateOptions<Abblix.Oidc.Server.Common.Configuration.OidcOptions>

Inheritance System.Object → RegistrationRequestSizeValidator

Implements Microsoft.Extensions.Options.IValidateOptions<OidcOptions>

Remarks

A non-positive limit takes the endpoints down rather than bounding them, and it does so differently on each host: an MVC host answers 413 to every registration, including a valid one of a few hundred bytes, while a minimal API host hands the value to a server that rejects it and answers 500. Neither reads as a configuration error at the point it surfaces, and both look to an operator like the endpoint being broken.

Zero is refused alongside a negative value because it means the same thing here: a request body always carries at least the two braces of an empty JSON object. A deployment that wants no bound of ours clears the option instead, which this validator lets through.