quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Developer’s guide

18. Certificates, DNS and Azure URLs

A correct hostname and a trusted certificate are separate requirements. DNS chooses where to connect; certificate verification establishes that the peer is allowed to serve that name. Changing one does not replace the other.

Trust domains

Public trust material Purpose
Quinzee Development Root CA Native quinzee.cloud/service names and the localhost application UI
Quinzee Azure Emulation Root CA The explicitly supported Microsoft/Azure hostnames inside a development environment
Engine CA PostgreSQL, MySQL and cache hostnames; maintained by the separate supervisor
Functions runtime CA Private gateway-to-host HTTPS; maintained by the separate Functions helper
Local telemetry CA Grafana and the OTLP collector

These CAs have private signing keys that stay with their owner. Clients need only public .crt files or a public trust bundle. The HTTP server receives its own leaf certificate/key, not a CA key. Application settings and leaf keys must not be copied into a shared image.

The application helper creates its certificates under .local/application/development/certificates, and puts the client's public bundle in client/trust.pem. The standalone cloud uses .local/certificates. Mixing these environments is a common cause of TLS failures.

Native and Azure addresses

Service Azure URL/name in the prepared container Native local name
Identity login.microsoftonline.com quinzee.cloud:11443 (tenant paths)
ARM management.azure.com quinzee.cloud:11443
Blob <account>.blob.core.windows.net <account>.blob.storage.quinzee.cloud:11443
Queue <account>.queue.core.windows.net <account>.queue.storage.quinzee.cloud:11443
Table <account>.table.core.windows.net <account>.table.storage.quinzee.cloud:11443
Service Bus AMQP <namespace>.servicebus.windows.net:5671 <namespace>.servicebus.quinzee.cloud:5671
Functions HTTP <app>.azurewebsites.net <app>.functions.quinzee.cloud:11443
Key Vault <vault>.vault.azure.net <vault>.vault.quinzee.cloud:11443
App Configuration <store>.azconfig.io <store>.appconfig.quinzee.cloud:11443
PostgreSQL <server>.postgres.database.azure.com:5432 <server>.postgres.quinzee.cloud:5432
MySQL <server>.mysql.database.azure.com:3306 <server>.mysql.quinzee.cloud:3306
Redis-compatible cache <cache>.<region>.redis.azure.net:10000 <cache>.redis.quinzee.cloud:10000
Monitoring ingestion dc.applicationinsights.azure.com dc.monitor.quinzee.cloud:11443
Monitoring queries api.loganalytics.azure.com, api.loganalytics.io, api.applicationinsights.io api.monitor.quinzee.cloud:11443

HTTP services use HTTPS; native SQL/cache ports use their own TLS protocols. The table's native HTTP port is the default. Prefer resource/deployment output endpoints so port overrides and returned names remain correct.

Service Bus uses a separate AMQP/TLS listener; its HTTPS messaging API uses the normal cloud HTTPS port on the namespace host. Functions clients trust the public cloud gateway, not the private runtime CA. The helper verifies its own upstream connection. Existing installations need refreshed leaf certificates for newly supported service names; if the constrained Azure CA changes, refresh that public CA in clients that explicitly use Azure emulation too.

The Azure listener uses port 443 inside the private Docker network. It is not exposed as your host's public port 443. Therefore changing a host's DNS alone is not sufficient to make an unmodified host SDK use the container listener. The client-container approach provides the right network reachability, DNS and trust without changing the host.

Enable Azure names on a standalone cloud

  1. Run make cloud-up on the host. It prepares the native and constrained Azure leaf certificates and starts cloud/DNS.
  2. Connect QHQ to this instance, open Emulator → DNS, enable Azure emulation and apply the change.
  3. Join your client container to triglav-http_quinzee and set --dns 172.29.53.53, unless you changed the standalone network settings.
  4. Trust the public Azure-emulation CA in that client. Add the engine CA as well if using SQL/Redis. Never mount CA private keys.
  5. Confirm DNS gives the emulator address and verify /health before sending development credentials.

For the book's application environment, the helper already performs these steps with its own private network. Use the dynamic values from chapter 3. Unsupported Azure names continue resolving normally; this is not an offline replacement for all Microsoft endpoints. Only use explicit local application credentials, not your production account, for emulator exercises.

Certificate lifecycle

Standalone certificates are prepared by make certs; the Azure certificate is also prepared by make cloud-up. Valid existing certificates are reused. Leaf certificates have a 90-day development lifetime. Engine certificates and telemetry certificates have their own owners and renewal procedures.

If certificates predate newly supported hostnames, a still-valid leaf may not contain those names. Deliberate regeneration of standalone certificates with make certs FORCE=1 replaces trust material: stop affected work, preserve any needed backup, restart the services and update every client's public trust bundle. Do not use this command as a routine response to an unrelated 401. The application environment's certificates require using its own directory; the default make certs does not update them.

Never use curl -k, a permissive certificate callback or a disabled hostname check to work around a setup error. Keep the supervisor running for the native engine CRL endpoint so clients can retain revocation verification.