Tenant Link Schema
Felder
Tenant Link Schema
Consent-based federation link between two Codemeta tenants, possibly on different installations (ADR 0445)
label
Display name for the connection list. Never sent over the wire.
peerKind
local = another tenant of this installation (loopback, no secrets); remote = a foreign installation (signed HTTPS).
localremotebaseUrl
Remote only. HTTPS enforced and re-validated against assertSafeOutgoingUrl before every call (SSRF).
peerInstallationId
Opaque id of the counterpart installation, stamped during the handshake.
peerTenantId
Counterpart tenant. Stamped on redemption only — never client-writable.
invitationCode
Server-generated invitation. Unique while pending, cleared on redemption. Redacted from every read.
invitationExpiresAt
After this instant the code no longer redeems.
status
pendingacceptedrevokedrevokedSide
Which side ended it. Both sides may revoke.
initiatorpeerroles
mspTenantId
customerTenantId
partyId
THE anchor — the customer party in the MSP CRM. Never leaves the installation.
protocolVersion
Negotiated major version, min(local, peer).
capabilities
What the PEER may do here. Server-enforced.
createTicket
comment
changeStatus
changePriority
requestReturn
peerCapabilities
What we may do there. Display / pre-flight only — never an authorisation basis.
inboundKeyId
NON-SECRET selector (X-Codemeta-Peer-Key). Installation-wide unique — the ingress knows no tenant yet.
inboundSecretEnc
AES-256-GCM blob of the secret inbound signatures are verified with. Encrypted, NOT hashed — HMAC verification needs the plaintext.
inboundSecretRotatedAt
outboundKeyId
The counterpart's selector — what we send in X-Codemeta-Peer-Key.
outboundSecretEnc
AES-256-GCM blob of the secret outbound signatures are created with.
outboundSecretRotatedAt
exchange
TicketExchangeConfig (ADR 0363 §1b) — target, statusMap, priorityMap. Same type as the Jira side.
acceptedAt
acceptedBy
revokedAt
revokedBy
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/tenant_links— Liste, paginiert + filterbarGET /api/v1/tenant_links/<id>— Einzelne EntityPOST /api/v1/tenant_links— AnlegenPATCH /api/v1/tenant_links/<id>— Teil-UpdateDELETE /api/v1/tenant_links/<id>— Soft-DeleteGET /api/v1/tenant_links/<id>/timeline— Audit + Aktivitäten