KodeMed License Portal (internal)

1 Who the licence is for

#1572 — licences are issued for an organization. Pick the Org record; its stable orgId is baked into the signed licence and is what ties the licence to the customer everywhere else in this portal.

Organization *

Organization name *

Licensee contact (optional)

Instance id (optional) Fill this in whenever a customer runs more than one KodeMed — prod and staging, or one per site. It is written into the signed licence and it is the only thing that tells two otherwise identical licences apart in Issued licences and in Subscriptions (one active subscription per organization + instance). Leave it blank for a single-instance customer.

2 Licence terms

License type

Valid until *

Max concurrent users

Server components

3 Modules

4 Catalog year

Calendar year

Resolved catalogue versions

—

orgId	Display name	Legal name	UID	Contact	Status	bexio	Harbor pull
Loading…

Role	Name	Email	Phone	Title
Loading…

Organization	Instance	Hostname	Type	Provider	DB	Region	Modules	Year	Users	Expires	Licence	Status
Loading…

What an organization is entitled to — who may run what, on which hostname, with which modules, until when. It is not the live infrastructure: the VM, namespace, IP and running image stay with the control plane. The control plane reads these records to know what it may provision.

Organization *

Status

Hostname (contracted)The address the hospital will actually use, e.g. kodemed.spital-muster.ch. The provisioner derives the rest from it — api., data. and grouper. subdomains, the TLS certificate and the DNS records — so it must be a name whose zone we can manage. Host only: no https://, no path.

Instance idWhich deployment of this organization. One organization may run several at once — typically prod alongside staging, or one per site — and each needs its own subscription. One active subscription is allowed per organization + instance id, so reuse the id only when replacing that same deployment. Short and lowercase: prod, staging, site-a.

License type (renewal)

Provider

DB mode

Region

Modules

Catalog year

Max users

Expires on

Current licence id (optional)

Version	Release date	State	Published	Notes (langs)
Loading…

Issued	Organization	Org link	Instance	Type	Modules	Year	Users	Expires	By	Assigned to
Loading…

Username	Name	Email	Enabled	Licences (a user can hold several)
Loading…

Health	Domain	Organization	State	Version	Provider	Region	Instance id	Actions
Loading…

Cluster	Domain	Organization	State	Version	Tier	Last job	Last backup	Cert
Loading…

When	Action	Tenant / ref	Who	Detail
Loading…

Harbor registry credentials (per-instance robot tokens — #1604)

Not applicable to this deployment. This panel configures the control plane's Harbor credentials, used to mint per-instance robot tokens during SaaS provisioning. No control plane is configured on this server (kodemed.license-portal.control-plane.base-url), so there is nothing to save to — the form is hidden rather than left editable.

To give a customer a Harbor pull credential, use Organizations → Harbor access instead. That one is issued by this portal directly and is configured with the LICENSE_PORTAL_HARBOR_* environment variables.

Used for: Minting a pull-only Harbor robot token for each provisioned instance, while the SaaS control plane provisions it.
Used by: The SaaS control plane — not this portal, and not the customer. Stored encrypted in the control plane.
Registry: —
Project: —
Robot-manager: —
Stored password: —
Per-instance tokens: —
Source: —

Registry

Where the robot tokens are minted, and which project they are scoped to.

Harbor URLBase URL of the Harbor registry, e.g. https://harbor.mieresit.com. Must be https: over http Harbor answers 301 with an HTML body, which the control plane cannot parse and reports as invalid Harbor JSON response. Change it here whenever Harbor moves — no redeploy, no env file.

ProjectThe Harbor project the minted tokens may pull from, and nothing else. Use the customer-facing project (kodemed), not the internal one — a tenant must never be able to pull development images. Blank uses kodemed.

Robot-manager account

The Harbor account allowed to create robots. The password is write-only — it is never sent back to this page, so leaving it blank keeps the stored one. Typing one here replaces it when you save.

Admin username

Admin password

Issued token policy

What the minted per-instance tokens look like. Turning this off makes every new instance fall back to the shared pull secret — existing instances keep the token they already have.

Robot token expiry (days)Lifetime of each minted token. Shorter means a leaked token stops working sooner, but an instance whose token expires can no longer pull images — it keeps running and fails on the next restart or upgrade. -1 means never expires. Default 30.

Per-instance robot tokens

Overwrites the stored control-plane credentials.

KodeMed License Portal

Licence issued and downloaded

Contacts

Send email to a contact

Notes (internal — newest first, append only)

Audit log

Registry

Robot-manager account

Issued token policy