ApplyOverlayUrisDto

Namespace: Meshmakers.Octo.Communication.Contracts.DataTransferObjects

Request body for POST {tenantId}/v1/clients/{id}/overlayUris — declares a set of overlay URIs to apply to the three URI list attributes of a blueprint-managed ClientDto. The endpoint dedupes by URI string (any source) and writes new entries with Source = "overlay:<OverlayName>", so the Step 2a preservation pass keeps them across blueprint re-apply and the future DumpTenant --clean filter can strip them from sanitised exports.

public sealed class ApplyOverlayUrisDto

Inheritance Object → ApplyOverlayUrisDto

Properties

OverlayName

The overlay name suffix that goes into the materialised Source = "overlay:<OverlayName>" marker. Operator-meaningful (e.g. "local-dev", "gerald-laptop"). Constrained to [A-Za-z0-9._-]+ to match the identity-services ClientUriSources.OverlayPrefix contract and the future DumpTenant --clean filter regex.

public string OverlayName { get; set; }

Property Value

String

RedirectUris

URIs to add to RedirectUris. Null / empty list = no changes to that list. Each URI is deduped against the existing list contents (any source); duplicates are silently skipped.

public List<string> RedirectUris { get; set; }

Property Value

List<String>

PostLogoutRedirectUris

URIs to add to PostLogoutRedirectUris. Same dedup rule as ApplyOverlayUrisDto.RedirectUris.

public List<string> PostLogoutRedirectUris { get; set; }

Property Value

List<String>

AllowedCorsOrigins

CORS origins to add to AllowedCorsOrigins. Same dedup rule as ApplyOverlayUrisDto.RedirectUris. The endpoint does NOT auto-strip trailing slashes — the caller is responsible for passing origin-shaped values (no path / trailing slash) so IdentityServer's ValidatingClientStore accepts them.

public List<string> AllowedCorsOrigins { get; set; }

Property Value

List<String>

Constructors