Changelog

Was ist neu in ip·Solis

Nur die Highlights — Upgrade-Hinweise und Migrationsschritte stehen in der Doku.

v0.7.1
  • Air-gapped runtime. The browser now loads nothing from external CDNs — all CSS, JavaScript and fonts are served from the ipSolis host. Tailwind is compiled during the Docker image build (a `node:20-alpine` stage) into a local stylesheet; htmx, the Monaco script editor (whole `vs/` tree) and the Inter font are vendored under `/static/vendor/`. Internet is required only to build the image or `docker pull` a prebuilt one. Optional `CSP_ENABLED` flag adds a self-only Content-Security-Policy; a CI guard fails the build if any external asset origin reappears. No visual/behaviour change (one pre-existing latent bug fixed: the standalone auth pages now render their surface colors). See the new *air-gapped runtime* note in the deployment guide.
  • Order justification. A free-text business justification, configurable per asset definition (collect on/off + required yes/no), shown to the approver on the decision page and in the approval email / Teams / Slack notifications.
  • Portal execution-step visibility, per asset definition. `off` (default — status only), `detailed` (step names/status/timing), or `debug` (adds raw step logs/errors for diagnostics).
  • External-secret resolution for SMTP. The worker's email send path now resolves an `email.password` stored as a `vault://…` / `ccp://…` reference (previously only the *Test SMTP* button did, so an externalized SMTP credential passed the test but failed on real sends).
  • Adds `0013` (order justification: `orders.justification` + two `asset_types` flags) and `0014` (`asset_types.portal_step_visibility`). Both additive (nullable / defaulted columns; no backfill).
v0.7.0
  • Drift / out-of-band reconciliation (AD). A Beat task periodically re-reads the AD groups that `drift_monitor` asset types provision into and compares actual membership against what ip·Solis granted (from the order change log). Divergences — *missing access* (granted, removed in AD) and *out-of-band* (added directly, never granted) — are recorded to `drift_findings`, audit-logged (streamed to the SIEM), and surfaced on Operations → Drift. Opt-in per type; global schedule + `detect_only` / `auto_remediate` mode under Maintenance → Drift reconciliation; auto-remediate re-grants / revokes via AD. Best-effort email/Teams alert.
  • Software license & contract lifecycle. New `SoftwareContract` entity (vendor, product, value, billing interval, licensed seats, renewal date, notice period) bound 1 : N to asset types. The cost report prices each active order at the contract's per-seat rate (contract value ÷ seats) instead of a flat monthly cost, and tracks utilization + unused-seat shelfware and seat over-allocation (Model A — actual consumption). New Reports → Licenses & Contracts page; daily opt-in renewal-reminder Beat task fires when a contract enters its notice window.
  • Slack approval delivery. Approvals can post a Block Kit message to Slack in parallel with email (and Teams), reusing the same channel-agnostic signed one-click approve link. Config `slack.mode` / `slack.webhook_url` + Settings section + test button; covers initial dispatch and reminders.
  • Signed attestation artifacts. Optional per asset type: a handover acknowledgment (Übergabeprotokoll) on provisioning — the recipient gets a signed link to confirm receipt (and an acceptable-use policy) — and a revocation / disposal certificate on revoke/expiry (audit evidence of what was removed). Signed-token HTML pages (archival via print); reviewed under Reports → Attestations; overdue-ack reminder Beat task.
  • Onboarding bundles & assignment rules. A `Bundle` groups existing asset definitions into a package; an `AssignmentRule` maps user attributes (department, cost center, …) to a bundle (reusing the approval-rule condition format). Ordering a bundle creates one lightweight `OrderGroup` with one order per position through the normal approval/execution paths (idempotent — asset types the user already holds are skipped). Triggerable from Onboarding admin (evaluate for a user), the self-service Packages catalog, a SCIM joiner, and optionally a user's first portal login (`onboarding.eval_on_first_login`).
  • SCIM joiner/mover provisioning. Extends the SCIM endpoint from leaver-only to full joiner/mover/leaver: a new `ScimIdentity` last-seen projection; `POST/PUT /Users` (opt-in `scim.joiner_enabled`) evaluate assignment rules and order matched bundles; a mover (attribute change) reconciles entitlements via `scim.mover_mode` (`disabled` / `additions_only` / `reconcile`), where reconcile also revokes lost entitlements — strictly limited to rule/SCIM-provisioned orders (self-service and manual orders are never auto-revoked).
  • Entra group provisioning (Microsoft Graph). The `entra_group` access-target type now grants / revokes Entra (cloud-only) security-group membership via Microsoft Graph (app-only, dedicated `graph.*` app registration). Closes the gap between Entra *login* (OIDC) and *provisioning* Entra groups for M365 / cloud-only customers. Settings card + Test Credentials.
  • Portal accessibility (structural). Skip link, `main` landmark + labels, decorative-icon `aria-hidden`, live notification badges, an early `lang` binding, and keyboard `:focus-visible` outlines across the shared portal templates — no visual redesign. Closes the BITV / EN 301 549 structural basics (portal only; not a formal conformance claim).
  • SCIM full filter grammar (RFC 7644 §3.4.2.2). `GET /Users?filter=` now supports the full grammar (`eq ne co sw ew gt ge lt le pr`, `and` / `or` / `not`, grouping) instead of only `userName eq`; a malformed filter returns `400 invalidFilter`. Added a read-only `/Groups` shim (empty list; group membership lives in AD, not SCIM).
  • Access-target validation. Saving an asset type now rejects access-target types without a provisioning handler (only `ad_group` / `entra_group`; `rds_collection` / `other` → 400).
  • Adds `0004`–`0012`: drift findings + per-type flag; software contracts + `asset_types.contract_id`; Slack config; attestation artifacts + flags; onboarding bundles / assignment rules / lightweight `order_groups` + nullable `orders.order_group_id`; SCIM identity projection; SCIM mover config; Graph (`graph.*`) config; onboarding first-login config. All additive (new tables + nullable columns + seeded config); no backfill of existing rows.
  • Feature-alert emails now send from the configured `email.from` address instead of the container's `MAIL_FROM` default, so drift / contract-renewal / attestation alerts match the rest of the platform's outgoing mail identity.
  • Autonomous feature-test harness (`tests/feature/`). A self-contained integration suite (58 tests) drives the running stack end-to-end over HTTP + DB and a testlab mock-receiver: order lifecycle (provision / modify / revoke / all deprovision policies, capacity, scheduled, ServiceNow-webhook HMAC), access provisioning against real AD and mock Microsoft Graph, drift detection, approvals + certification (incl. auto-revoke), HR leaver, SCIM JML, onboarding bundles, software-contract cost math + renewal, attestation emission/ack, cost & point-in-time access reports, LDAP portal login, real Teams delivery, and every Beat cycle. Namespaced and self-cleaning; not shipped in the runtime image.
v0.6.15
  • Licensing terms & texts updated for the free-tier / volume-band model (reviewed and approved). The XenPool Commercial Source License (`LICENSE`, EN + DE), the German `AGB` and the English `Terms`, plus the README and deployment/onboarding docs now reflect the sales model enforced since 0.6.14: free productive use for up to 25 active users (including in an organizational context), with commercial use (more than 25 active users) licensed in volume bands by active-user count. Adds an authoritative *active user* definition; the license scope wording changed from "licensed instances" to "licensed number of users / volume band (max. Active Users; 0 = unlimited)"; after expiry + the 30-day grace the software reverts to the Free Tier (no longer described as "evaluation only").
  • In-app license texts & shop links. The dashboard unlicensed-state banner is now a "Free tier · up to 25 active users" banner; the Maintenance license card explains the tiers and bands. All purchase / renewal calls-to-action now point to the ip·Solis license shop (locale-aware: `…/en/shop` / `…/de/shop`) instead of a sales email; `sales@xenpool.de` is retained only for inquiries, support and the imprint.
v0.6.14
  • Free-tier / commercial-band user-count enforcement. A free productive tier allows up to 25 active end-users without a license; a valid commercial license raises the limit to its signed `max_users` band (e.g. 75 / 250; `0` = unlimited). "Active user" = a distinct (case-insensitive) `orders.user_email` on an order in an active status. Enforcement is soft: existing operation is untouched — only the creation of an order for a new (not-yet-counted) identity is blocked once at/over the limit (HTTP 403 across the portal, `/orders` API and the ServiceNow webhook). The Admin Dashboard shows a banner (red at the limit, amber from 80 %). The band rides on the existing 30-day license-expiry grace; demo/evaluation licenses never raise the limit. New endpoint `GET /admin/tier/status`.
  • Evaluation-license recognition & display. Demo/evaluation licenses (signed by the demo key) are now labelled as such: a dashboard "Evaluation license" banner and an "Evaluation" badge on the Admin → Maintenance → License card, with licensee and validity.
  • Built-in tile-icon picker for asset definitions. A bundled set of monochrome IT icons (Desktop/VDI, Laptop, Server, VM, Database, Mailbox, Application, License, Smartphone, Monitor, Cloud, Storage) selectable directly in the asset-type form — no upload needed. Stored as a data-URL like an uploaded logo, so the portal catalog renders them unchanged.
  • Reassign an asset definition while Free. Operators can change a personal asset's Asset Definition inline in Personal Assets, but only while the asset's status is `Free` (UI dropdown + server-side guard; rejected with 409 otherwise).
  • Unimplemented Access Target types marked "coming soon". In the asset-type form, *Entra Group*, *RDS Collection* and *Other* are now disabled and labelled "(coming soon)" — only *AD Group* is implemented end-to-end (the others were selectable but failed silently at provision time). Backend status documented in `TASKS.md`.
  • Admin Settings — OIDC provider field labels. Provider-ID placeholder aligned with the Entra example, and a help line added under *Client ID*.
  • Integrations docs — SMTP authentication options. New section (EN + DE) clarifying that ip·Solis is provider-agnostic SMTP-only (no vendor send APIs), with a decision table (relay vs. app password) and an M365 caveat recommending a relay for a future-proof setup.
  • HTTPS OIDC redirect URIs behind the reverse proxy. uvicorn now runs with `--proxy-headers --forwarded-allow-ips=*` so it honours nginx's `X-Forwarded-Proto`; previously the app derived `http://` callback URLs, breaking SSO with `AADSTS50011`. Image build/push/cache and tags are unchanged.
  • Admin status banners in dark mode. On reset, the `dark:` red/blue colour classes were not cleared, so a successful test (AD/SCCM/email/compliance) could render red. Banners now reset to base classes before applying the new state.
  • `test_asset_type_constraints.py` realigned with the migration-0047 validator (two create-time rules; runbook-wiring is now a dispatch-time concern) — the suite previously targeted the removed 5-rule API.
v0.6.13
  • Admin Users — masked password reset. The "Reset password" action now opens a dedicated modal with a masked input and a show/hide (👁) toggle, replacing the native browser `prompt()` that always displayed the new password in cleartext. The same show/hide toggle was added to the Create-user password field for consistency.
  • Production overlay renamed: `docker-compose.prelive.yml` → `docker-compose.prod.yml` to match its actual role (the TLS/nginx production overlay; the old `prelive` name was historical and misled operators). All references updated — CI (`deploy-prelive.yml`), `docker-compose.ghcr.yml` usage comments, `tools/install/bootstrap-certs.sh`, `README.md`, and `docs/DEPLOYMENT.md`/`.de.md` (the `COMPOSE_FILE` examples now use `docker-compose.prod.yml` and the interim "historical name" clarifying comments are removed). The prelive *environment* and its deploy workflow keep their names — only the overlay file was renamed. Operator action: hosts that pin the overlay via `COMPOSE_FILE` (e.g. LinPre1/LinPre3) must update the filename; there is no back-compat alias.
  • Deployment guide clarified for first-time installers. The TLS section now states explicitly that certificate Options A/B/C are mutually exclusive alternatives, with an "end of options" callout before *Configure nginx* (the shared step). The *Start the Stack* intro was simplified — dropped the `locales/`/`scripts/` baked-in internals and version wording that confused first-time installers, keeping only pull/start and the prod-pin-vs-latest choice. (EN + DE)
  • CI: stop uploading buildx `.dockerbuild` build records. The release workflow now sets `DOCKER_BUILD_RECORD_UPLOAD=false` (and `DOCKER_BUILD_SUMMARY=false`) at job level so the API and Worker `build-push` steps no longer emit the `.dockerbuild` artifacts that were accumulating on every release. Image build, push, cache, and tags are unchanged.
v0.6.12
  • Aligned and clarified the license wording across the documentation, the bundled `LICENSE` copies, and the Admin UI so they are consistent with the Terms.
v0.6.11
  • Deployment guide is now prebuilt-image (GHCR) only. `docs/DEPLOYMENT.md` documents a single supported install path — pulling the public `ghcr.io/xenpool/ipsolis-{api,worker}` images — and drops the build-from-source variant throughout (start, update, HA, troubleshooting, clean reset). The image tag now defaults to `:latest`, with per-environment guidance: pin `IPSOLIS_VERSION` in production, track `:latest` in pre-live / test.
  • License module docstring clarified. `max_users` / `max_asset_types` are parsed for display only and are not enforced at runtime (no feature/usage gating — all features ship in every edition). Corrected the misleading "enforces …" wording in `api/app/utils/license.py` and the byte-identical worker copy.
  • License documentation corrected. The README's License section incorrectly claimed AGPL-3.0 / a "dual-licensed open core". ip·Solis is in fact source-available under the XenPool Commercial Source License v1.0 (free for non-commercial use + 30-day evaluation; commercial use requires a purchased license). Removed all AGPL references and aligned "open-source" wording to "source-available".
  • Deployment guide: `sudo chmod +x` for the mkcert binary (it is downloaded as root via `sudo curl`, so the non-sudo `chmod` failed with "Operation not permitted"); replaced the misleading `acme.com` example hostname with `example.com`.
v0.6.10
  • Provider-agnostic portal SSO (generic OIDC). The self-service portal now authenticates users against any standards-compliant OpenID Connect identity provider — Entra ID, Okta, Ping, Google, Keycloak, Authentik, Zitadel, … — through a single code path. Each provider self-configures from its issuer URL via the discovery document (`<issuer>/.well-known/openid-configuration`); adding an IdP is a config entry, not a vendor integration. New helper `api/app/utils/oidc.py` validates ID-token signatures against the provider JWKS (PyJWT) plus iss/aud/exp and the OIDC nonce.
  • OIDC provider registry. Providers are stored in `app_config` under `idp.<id>.*` (unlimited providers, stable URL-safe ids). Admin → Settings → Authentication gains an add/edit/delete provider UI with a Test button that runs a discovery probe. New endpoints: `GET /admin/config/oidc/providers`, `PUT/DELETE /admin/config/oidc/{provider_id}`, `POST /admin/config/oidc/{provider_id}/test`, `PUT /admin/portal-auth`.
  • Login method picker. When more than one login method is enabled the portal shows a chooser at `/portal/login` (fully localised, 5 locales); with exactly one it redirects straight to it.
  • On-prem LDAP portal login. Username/password login against on-prem AD/LDAP, offered alongside OIDC via `auth.ldap_enabled` (folds in the earlier short-lived `onprem_ldap` mode).
  • Reuse existing tile logos. The asset-definition form gains a "Choose existing" logo picker that reuses any logo already attached to another asset type (deduped), no re-upload. New endpoint `GET /admin/asset-type-logos`.
  • Prebuilt-image install (GHCR). New `docker-compose.ghcr.yml` pulls the public `ghcr.io/xenpool/ipsolis-{api,worker}` images instead of building — faster, version-pinned installs (`IPSOLIS_VERSION`). `locales/` and `scripts/` are now baked into the images (root build context + `.dockerignore`) so a prebuilt install needs no repo checkout of them.
  • Parametric OIDC callback. Portal callback is now `/portal/auth/{provider_id}/callback` (was the Entra-only `/portal/auth/callback`). Logout is generic RP-initiated logout via each provider's `end_session_endpoint`.
  • Portal auth gate. Replaced the Entra-specific `entra.mode` with `portal.auth_required` (login on/off) + per-provider `idp.<id>.enabled` + `auth.ldap_enabled`. Migration `0003` seeds the toggles and migrates any existing `entra.*` config into `idp.entra.*`. Service-health probe `entra` renamed to `sso` (probes discovery for every enabled provider). SAML 2.0 remains out of scope (separate task).
  • Admin sidebar layout. Audit Log and API Tokens moved into the compact footer section; theme toggle + signed-in user moved to a sticky top-right header — frees vertical space so the nav no longer needs an internal scrollbar.
  • Script modules are PowerShell-only. The Script-type dropdown is removed (Python/Bash were never functional — the worker injects a PowerShell-only `$VARS`/`$PARAMS` preamble); the API coerces `script_type` to `powershell`. Module + runbook editors are now English-only.
  • Login-settings save returned 422. `PUT /admin/config/portal-auth` was shadowed by the generic `/config/{key}` route (parsed as a config key, rejected the body as missing `value`). Moved to `PUT /admin/portal-auth`.
  • Portal i18n on prelive. Locales are now baked into the api image, so prelive's `volumes: []` ("baked code") no longer leaves `/app/locales` empty (i18n had silently fallen back to English).
  • nginx config + SSL paths. Mount `nginx.conf` to `conf.d/default.conf` (not the main `nginx.conf`); unified the SSL cert path to `nginx/ssl/` across all compose files and docs.
  • Docs: corrected all "`alembic upgrade head` is automatic" references (it is not); wrapped long `docker compose` commands; added the first-install alembic step + an SSL pre-flight to the update section.
  • Entra-only MSAL login path. `api/app/utils/entra.py` and the `entra.*` config keys are retired; the generic OIDC path supersedes them (no MSAL-only feature was in use). `msal` is retained only for the legacy Entra credential test.
  • `entra_with_onprem` auth mode. Removed entirely (never fully implemented; no production deployments).
  • Build images from the repo-root context so shared `locales/`+`scripts/` can be baked; added `.dockerignore` to keep secrets (`.env`, `licenses/`, `backups/`, `nginx/ssl`) and `.git` out of the images.
  • GHCR packages made public (anonymous pull); `actions/checkout` v4 → v5 (Node 20 deprecation).
v0.6.9
  • Update Notifier: "Check now" button. Triggers an immediate update check from the Settings page without waiting for the daily Beat tick. Shows inline feedback: "Up to date", "New version available: vX.Y.Z", or the actual error text — auto-fades after 5 s on success.
  • Update Notifier: GitHub Release created on tag push. `release.yml` now includes a `create-release` job that extracts the matching CHANGELOG section and publishes a GitHub Release after images are pushed. Previously only a git tag was pushed, causing `releases/latest` to return 404.
  • Update Notifier: 404 no longer shown as error. When the GitHub repo has no published releases yet, the checker now clears the error field and logs "no releases yet" instead of recording a failure.
  • Update Notifier: error box shows actual error text. Settings page previously displayed the static "See server logs for details" message regardless of the real error. Now shows the stored `updates.check_error` value.
v0.6.8
  • Portal nav badges. My Approvals, Delegations, and Access Reviews now show a live count badge (red / amber) when the signed-in user has pending items. Loaded via `GET /portal/nav-badges` (3 parallel COUNT queries) on every page without touching existing route handlers.
  • Retry failed orders. Admin order detail shows an amber "Retry now" button when an order is in `failed` state. Clears the step history, resets the order to `processing`, re-dispatches the runbook, and writes an audit row.
  • Audit log: admin cancel now records the acting user. `POST /ui/orders/{id}/cancel` was missing `request: Request`, so the audit `triggered_by` showed `celery:dynamic_runner` instead of the admin session. Fixed.
  • Admin order detail: Admin Actions moved above Execution Steps. Cancel / Extend / Retry panel now appears directly below the user and asset cards, before the step log.
  • Docs: ServiceNow webhook fully documented. `integrations.md` section rewritten from a 4-line stub to a complete integration reference: both auth methods, full payload schema, `curl` example, complete response JSON, capacity checks, idempotency, error table, and audit trail. Fixed incorrect scope name `webhook:servicenow` → `webhook:in`.
v0.6.7
  • Portal approval notice. When an asset type requires manager or application-owner approval, an amber info bar now appears on the order form before the user submits. Message text adapts to the approval combination (manager / owner / both) and switches language live without a page reload.
  • Hard-delete revoked API tokens. Superadmins can now permanently remove individual revoked token rows via a ✕ button on the API Tokens page. The endpoint (`DELETE /admin/api-tokens/{id}/hard`) requires the token to be revoked first and writes an audit row before deleting.
  • Conditional approver AD validation. Rule-configured approver emails are now validated against Active Directory at order-creation time (same as manager approval). Orders are blocked with a clear error if a configured approver cannot be resolved as a valid domain account. AD-canonical display name and email are used in all notifications.
  • Docs: Approval Workflow and Conditional Approval Rules. `docs/web/self-service.md` now contains a full reference for all three approval types, quorum (N-of-M), per-rule quorum groups, approver deduplication, SoD exemption, condition field reference (built-in + `attr.<key>` custom fields), operators, compound logic (ALL/ANY/NOT, max depth 8), and three worked examples.
  • Docs: Parameter system and Parse-from-Script. `docs/web/automation.md` now documents the `param_schema` structure, what the ↻ "Parse from Script" button does, the PowerShell-to-schema type mapping, and all three parameter scopes (PARAMS / VARS / CTX) with a full CTX key table.
  • Eligible Requestors DN can now be cleared. Editing an asset definition with the DN field empty no longer silently retains the previous value; the field is unconditionally written (`None` when blank).
  • Retention: FK constraint no longer poisons entire order cleanup batch. Orders referenced by `asset_pool.current_order_id` are now excluded from the retention DELETE via an `AND id NOT IN (...)` guard, preventing FK RESTRICT violations from aborting the whole batch.
  • Retention: one failing table no longer aborts the others. Each retention table is now wrapped in its own try/except and commits independently; a failure in one table is logged and reported but does not roll back the others.
  • Admin sidebar: three infrequently-used links moved to footer. Cost Report, Certifications, and Leaver Events are now rendered as small `target="_blank"` links in the sidebar footer, eliminating the scrollbar on standard viewport heights.
  • Admin sidebar footer: Documentation link added. A book-icon link to `https://www.ipsolis.com/en/docs` appears in the footer alongside Swagger UI.
v0.6.6
  • Legal: AGB and Terms revised (v2). Sections 1–16 substantively rewritten (free/commercial-use distinction, scope of owed performance, liability structuring). Draft notice removed. Anlage 1 / Annex 1 SBOM table retained.
v0.6.5
  • Legal: SBOM annexes now reference THIRD-PARTY-LICENSES.md. `AGB.md` Anlage 1 and `Terms-EN.md` Annex 1 intro text updated to declare `THIRD-PARTY-LICENSES.md` as the incorporated-by-reference source for full license texts and copyright notices; version reference updated to v0.6.4.
v0.6.4
  • THIRD-PARTY-LICENSES.md: replaced link-only table with complete license texts and copyright notices for all 96 Python dependencies, as required by MIT, BSD, Apache 2.0, and LGPL; generated via `pip-licenses --from=mixed --with-license-file`; includes infrastructure (Docker base images) and frontend (HTMX, Tailwind) sections
  • GitHub Actions: added `run-name` to `release.yml` and `deploy-prelive.yml` so workflow runs display the version tag instead of the commit message
v0.6.3
  • Admin login page: removed legacy `ADMIN_API_KEY` hint text and placeholder copy from the login form — the break-glass backend path still works but is no longer advertised publicly
  • AD service account docs: corrected "read-only" permission note to reflect that write access on group `member` attributes is required for group-based access assignment; added note that additional permissions depend on deployed modules and runbooks
  • Deployment docs (EN + DE): sudo fixes throughout — all writes to root-owned `/opt/ipsolis` now use `sudo`; `cat > file` redirections replaced with `sudo tee`; Option C auto-renewal section clearly marked; nginx config placeholder (`YOUR_HOSTNAME`) replaces hardcoded XenPool test hostname; docs now use `sudo sed -i` to substitute the placeholder
  • Deployment docs: `docker-compose.nginx.yml` renamed to `docker-compose.prod.yml` and expanded with api/worker production overrides (strip dev volumes, set uvicorn `--workers 4`); all references updated
  • Deployment docs: section 5 (compose overlay creation) replaced with a note that `docker-compose.prod.yml` is already included in the repository
  • Deployment docs: docker group prerequisite added to section 1 (`sudo usermod -aG docker $USER`)
  • Deployment docs: section 7 configuration checklist reordered to match the in-app Setup checklist; added missing items: "Set application title and logo", "Add at least one asset to the pool", Teams approval cards, SIEM, and per-integration API tokens
  • Deployment docs: beat scaling note moved from section 6 (stack start) to section 12.2 (HA / multi-replica worker) with explanation of `celery-redbeat` distributed lock
  • Deployment docs: section 7 mentions the included "Virtual Machine Recycler" example runbook as a starting template
  • `nginx/nginx.conf`: replaced hardcoded `ipsolis-pre.xenpool.local` with `YOUR_HOSTNAME` placeholder; added `client_max_body_size 2g`
  • AGB / Terms: completed SBOM (Annex 1) with all 35 dependencies across 9 categories, version-pinned with SPDX license identifiers; removed draft blockquote; added English convenience translation (`docs/legal/Terms-EN.md`)
  • TASKS.md: compressed 3100-line backlog into concise open-tasks + done-summary format; added `[open]` task for `onprem_ldap` portal auth mode
v0.6.2
  • `docs/DEPLOYMENT.de.md` — full German translation of the production deployment guide; code blocks and commands kept in English per technical documentation convention
v0.6.1
  • CI: docs/changelog updates now triggered by release tag only. The `trigger-docs-rebuild.yml` workflow (prelive-push based) is removed. The `release.yml` workflow now dispatches a `changelog-updated` event to ipsolis-web after images are pushed, triggering a production rebuild directly from the release tag.
  • Docs: PRO_FEATURES.md references removed. All links and references to the deleted `PRO_FEATURES.md` file replaced with inline descriptions in `DEPLOYMENT.md` and `README.md`.
  • Docs: Enterprise sizing tier renamed. Worker sizing table label "Enterprise" renamed to "Large" to avoid confusion with the retired Enterprise product tier.
  • Legal: AGB added. Full German terms and conditions for commercial ip·Solis licensing added at `docs/legal/AGB.md` (XenPool Commercial Source License, dual-track liability model, Munich jurisdiction).
v0.6.0
  • License tab: full license text. Maintenance → License now displays the full XenPool Commercial Source License in both English and German, replacing the previous "about" link. No external request needed — text is embedded in the template.
  • Edition cleanup: all remaining Pro / Community split artifacts removed. The `community` field is stripped from `BeatEntry` and Beat schedule entries; the PRO badge on the Beat schedule page is removed. Stale Pro Edition and community-install comments removed from `hr_webhook.py`. `enterprise_teaser` import and `nav_locked` calls removed from `base.html`. All residual "Pro Edition" / "Community Edition" copy removed from `.env.example`, testlab compose files, and docs.
  • Asset type form: section nav and copy. Section navigation behavior corrected; form copy improved for clarity.
  • `base.html` template errors. Orphaned `enterprise_teaser` import and stale `nav_locked` calls removed, resolving template rendering errors on pages that use the base layout.
v0.5.2
  • Edition collapse: Pro/Community split removed. All features are now available in a single public image. Commercial use requires a license under the XenPool Commercial Source License; non-commercial and evaluation use is free. The `PRO_FEATURES.md` doc is removed; the `ipsolis-community` repository is retired.
  • License UI: badge and copy updated. Dashboard shows "Unlicensed · Free for Non-Commercial Use" when no license is installed. Maintenance → License tab shows "Licensed / Unlicensed / No License" badges instead of "Pro / Community". All "Community Edition" references removed from UI and code.
  • Setup checklist: exclude migration placeholder values. Fresh installs no longer show false green dots for SMTP (`localhost`), AD (`dc.example.com`), and branding (`Ipsolis`) — the migration seed defaults are now excluded from done-checks.
v0.5.1
  • License: 30-day grace period after expiry. Pro features remain active for 30 days after a license expires, covering procurement delays and preventing operational outages from missed renewals. After the grace window the instance falls back to Community edition automatically. The daily Beat task (`license_check`) now fires a warning email each day during the grace period and a distinct "now running Community" alert once the grace period ends. Admin UI (License page) shows an amber warning banner throughout the window.
  • License: install UUID binding removed. Licenses are now portable across deployments — no `install_uuid` field in the payload, no per-install binding check, no reassignment limit. Eliminates the DB read on every Celery worker fork (`_register_install_uuid` signal handler), the `set_install_uuid` API startup call, and the "Install identity" card on the License admin page. Existing signed licenses without `install_uuid` continue to work unchanged; existing licenses that contained `install_uuid` are now accepted on any install.
v0.5.0
  • CI: upgrade `actions/github-script` v7 → v8. Fixes Node.js 20 deprecation on GitHub Actions runners (required from June 16 2026). Adds `permissions: {}` block and documents that `IPSOLIS_WEB_DISPATCH_PAT` needs `Contents: write` on `XenPool/ipsolis-web` for cross-repo dispatch.
  • Terminology sweep — Community / Pro (final pass). All remaining "Business" / "Enterprise" tier references updated across `release.yml`, `main.py`, templates, license utilities, `docs/DEPLOYMENT.md`, `docs/onboarding/INSTALL.md`, and `docs/web/*.md`. Community mirror strip list corrected: `standalone_runner.py` and internal CI workflows (`deploy-prelive.yml`, `trigger-docs-rebuild.yml`) added. Community mirror repo URL corrected to `ipsolis-community`.
  • GitHub community health files. Added `CODE_OF_CONDUCT.md`, `CONTRIBUTING.md`, `SECURITY.md`, `SUPPORT.md`, issue templates (bug report, feature request), and discussion template (Q&A).
v0.4.13
  • Web docs: Owner Ordering terminology. `docs/web/self-service.md` section renamed from "Deputy Ordering" to "Owner Ordering" to match the v0.4.11 UI rename. Description updated to clarify the Owner field identifies the beneficiary of the order, not a substitute approver.
  • Web docs: asset status label clarification. `docs/web/lifecycle.md` notes that the admin dashboard "In Use" tile and the asset pool list "Assigned" label both map to the underlying `busy` status.
v0.4.12
  • Edition docs aligned to Community / Pro. `EDITIONS.md` rewritten as a two-tier Community / Pro model (the three-tier Community / Business / Enterprise system was retired). `README.md` edition matrix updated: vSphere / XenServer moved to Community (never Pro-only per the build), standalone runbooks added as a Pro-only row, column renamed "Business" → "Pro". `docs/ENTERPRISE_FEATURES.md` renamed to `docs/PRO_FEATURES.md`; vSphere / XenServer section corrected from "Pro Edition only" to "Community Edition included"; stale "Enterprise license" and "Enterprise-gated" notes removed throughout.
  • Code comments and UI copy aligned. Stale "Enterprise feature" comments in `password_policy.py`, `approval_decision.py`, `beat_inventory.py`, `hr_webhook.py`, `admin_users.html`, `maintenance.html`, and `settings.html` updated to reflect that RBAC (ACL grants, SoD, password policy) and vSphere / XenServer are Community features. License expiry email copy updated to "Pro license". `docker-compose.testlab.yml` comment updated.
v0.4.11
  • Asset Owner concept. The portal's "Deputy / Stellvertreter" field is renamed to Owner / Besitzende (all five locales: en/de/es/fr/it) to reflect its real purpose: the person an asset is ordered *for* (e.g. an external user who lacks portal access), not a substitute approver.
  • Owner access to portal. Owners set via a MODIFY order now see the asset in My IT, My Orders, and the order detail/change/cancel pages — previously only the original provision order's `owner_email` was checked; a correlated EXISTS subquery now covers ownership established by any completed MODIFY.
  • + Add buttons on all user/group fields in the portal modify form (RDP Users, Admin Users, Owner) for discoverability alongside the existing Enter-key shortcut.
  • Asset type form hint. Amber warning below the "Enable RDP/Admin user list" checkboxes explains that these only show the portal fields; actual AD group writes require matching Group Targets with `principal_source: rdp_users` / `admin_users`.
  • Maintenance deep-link. `/ui/maintenance#license` now opens directly on the License tab via hash-based tab activation.
  • Approval gate on MODIFY is add-only. Re-approval is now triggered only when users are *added* to the RDP/Admin lists — removals (privilege de-escalation) go straight through without requiring approval. Comparison baseline fixed to use the latest completed MODIFY order rather than the original provision order.
  • Delegation self-approval prevention. When creating re-approval records for a MODIFY order, delegation is skipped if the resolved delegate is the same person who submitted the change, preventing self-approval loops.
  • Pro edition gating: portal logo. Custom portal logo settings are now gated behind the Pro license; Community installs see a `card_teaser` upgrade prompt.
  • Pro teasers: shop-first flow. All PRO teasers now link to the language-aware ip·Solis Shop (`/de|en|es|fr|it/shop` via `navigator.language`) with step-by-step Install ID checkout instructions. `sales@ipsolis.com` removed.
  • Maintenance License tab "How it works" updated: copy Install ID → visit shop → upload `.lic`. `sales@ipsolis.com` removed.
  • Owner field persistence. My IT detail page now reads `owner_email` / `owner_name` from the latest completed MODIFY order, so the set owner is correctly displayed after page reload (previously the provision order's empty value was shown).
  • Approval routing for owner-submitted changes. When the owner (not the requester) submits a MODIFY and the configured application-owner approver has a delegation active pointing back to the submitter, delegation is now skipped so the approval stays with the original approver.
  • Orphaned `license.html` template (no serving route existed) deleted.
v0.4.10
  • Migration squash. All 96 incremental Alembic migrations have been consolidated into a single `0001_initial_schema.py`. Fresh installs are unaffected. Existing instances (dev / prelive) require a one-time version stamp: `UPDATE alembic_version SET version_num = '0001';`
  • README. Quick Start section renamed from "Development" to "Local".
  • ORM model registry. Seven models previously missing from `models/__init__.py` (`ScriptModule`, `RunbookDefinition`, `RunbookStep`, `PsModule`, `GlobalVar`, `DbBackup`, `OrderChangeLog`) are now registered, fixing FK resolution in `alembic autogenerate`.
v0.4.9
  • Order creation 500 error. Placing an order via the portal, the `/orders` API, or the ServiceNow webhook raised `AttributeError: AssignmentModel has no attribute 'DEDICATED_SHARED'` because that enum value was removed in a prior refactor but the per-user quota guard in `portal.py`, `orders.py`, and `webhook.py` still referenced it. The dead conditional has been removed; `enforce_max_per_user` is now always applied.
  • License key rotation (commercial-2026). Updated Ed25519 signing key used to verify Pro license files.
  • Maintenance › License tab. Added `showBanner()` helper for consistent inline feedback messages on the license status panel.
v0.4.8
  • Update Notifier simplified. The configurable "Repository (GitHub API)" and "GitHub token" fields have been removed from Settings. The Community edition repo is now public on GitHub, so no token is required and the endpoint is hardcoded. Only the enabled / disabled toggle remains.
v0.4.7
  • Community example scripts (migration 0096). Three ready-to-use PowerShell script modules — `Example - Provision Asset`, `Example - Change Asset`, and `Example - Deprovision Asset` — are now seeded on every fresh install. They demonstrate the standard module pattern (param block, `$VARS` access, JSON output, try/catch) for use in asset-type runbooks.
  • Standalone Runbooks are now PRO-only. The sidebar nav item shows a locked PRO badge on Community installs; navigating to `/ui/standalone-runbooks` renders an upgrade teaser instead of the runbook list. The API route (`admin_standalone_runbooks.py`) and the Celery worker task (`standalone_runner.py`) are stripped from Community images at build time, and the Beat cron-schedule entry is omitted when the task is absent.
  • Script module seed data split by edition. The full set of production script modules (AD, SCCM, XenServer/XCP-ng, VMware, SQL) is PRO-only seed material. The community mirror now ships only `scripts/modules/examples/`; the `scripts/runbooks/` directory (Virtual Machine Recycler etc.) is also excluded from Community builds.
v0.4.6
  • PRO feature gating in Community edition. Community installs now show locked PRO badges (violet) on all PRO-only nav items and settings sections instead of either hiding them completely or granting full access. Affected surfaces: Certifications, Leaver Events (sidebar nav), SIEM (Settings → Compliance), SCCM (Settings → SCCM tab), and vSphere / XenServer (Settings → Hosting Infra tab).
  • Settings page layout broken for E-Mail, Compliance, SCCM, and Hosting Infra tabs. A missing `<div id="edit-modal">` outer wrapper in the Script Variables tab caused a stray `</div>` to close the main content container early, pushing every subsequent tab panel outside the page layout.
  • Dashboard banner incorrectly showed "PRO Edition" on Community installs. The edition check now requires `edition == 'pro'`; Community installs show no banner.
  • Certifications and Leaver Events appeared as active links in Community when running a non-stripped image (e.g. dev). Nav logic now gates on `edition` rather than `has_certifications` / `has_leaver_events`.
  • SCCM health probe called a stripped worker task on Community. `_probe_sccm` now short-circuits with `{"ok": null, "detail": "PRO feature"}` when `edition != "pro"`, matching the N/A display of unconfigured services.
  • `enterprise_teaser.html` unified to a single PRO tier (previously had separate ENT / BUS tiers with amber / blue distinction). All gated features now show a consistent violet PRO badge. The partial is no longer stripped from the Community Docker image so teasers render correctly without the PRO code present.
  • Community mirror workflow updated to retain `enterprise_teaser.html` in the public source tree (required for teaser rendering in community builds from source).
v0.4.5
  • add installation guide and environment variable setup ()
  • remove completed compose-rename migration runbook ()
  • remove orphaned and obsolete files ()
v0.4.3
  • add option to create AD groups if missing during grant ()
v0.4.2
  • Implement update notifier and password policy features ()
  • add PowerShell and bash scripts for release management ()
  • refresh license globals on config refresh ()
  • update project name to 'ip·Solis' across documentation and code ()
v0.4.1
  • RBAC slice 4 — password rotation, lockout, SoD per-rule opt-out, token mint guard relaxation. Operators can now configure forced password rotation (`rbac.password_rotation_days`, 0 disables) and lockout-on-N-failed-attempts (`rbac.lockout_threshold`, `rbac.lockout_duration_minutes`). Failed-login attempts are tracked per admin user; lockouts auto-expire after the configured window. Approval rules accept `sod_exempt: true` so a static compliance officer who is also an admin can sign off on orders for asset types they configured. `/admin/api-tokens` router gate relaxed from `superadmin` to `admin`; the existing mint guard prevents privilege escalation. `/admin/maintenance/*` GET endpoints now reachable by `auditor` for compliance review; writes still require `admin`.
  • RBAC (Community). Per-asset-type ACL grants, role-bound API tokens, SoD enforcement, and password policy ship in all editions. Community installs include the full role ladder, per-user accounts, scoped grants, role-bound tokens, enforced SoD, and password policy.
  • Testlab compose stack (`docker-compose.testlab.yml`) bundling Vault dev mode, rsyslog, and a mock SIEM/webhook receiver so SIEM / secret-backend / webhook integrations can be smoke-tested without paying the resource bill of full Splunk / Sentinel / CyberArk lab installs. Splunk Free is profile-gated (heavy image) and brought up via `--profile splunk` on demand.
  • Role-aware Admin UI navigation. Each nav item is gated by the signed-in admin's role so a helpdesk user lands on a clean 6-item nav instead of seeing every page and 403'ing on every click. Asset-type form shows a read-only banner with disabled Save button when the role can't write.
  • Runbook step editor — categorised module dropdown. Modules are grouped server-side by their `"CATEGORY - Name"` prefix (`<optgroup>`); description, category badge, parameter list, and an "Edit module ↗" deeplink render in a card below the dropdown instead of being squeezed into the option text.
  • Implement update notifier and password policy features ()
  • License changes refresh template globals immediately. Uploading or removing a license now refreshes the `is_enterprise` / `edition` / `license_info` Jinja env globals as part of the same request, so the Dashboard and feature-gated nav blocks reflect the new edition without an api restart.
  • Approval-delegations nav link gated to `admin`+ to match the API gate (the page is "admin manages delegations on behalf of users", not self-service).
  • Asset-type form result banner moved above the sticky save bar so 4xx responses (validation, role mismatch) are visible without scrolling past the bar pinned to the viewport bottom.
  • Vault testlab healthcheck — the alpine Vault image has no `wget`; switched the healthcheck to `vault status`.
  • `0073_rbac_slice4` adds three columns to `admin_users` (`password_set_at`, `failed_login_count`, `locked_at`), one column to `order_approvals` (`sod_exempt`), and seeds three policy keys (`rbac.password_rotation_days`, `rbac.lockout_threshold`, `rbac.lockout_duration_minutes`). All defaults disable enforcement so existing installs see no behaviour change.
  • `0074_update_check_config` (this release) seeds the update-checker feature config keys (`updates.check_enabled`, `updates.repo_url`, plus four cursor keys the daily Beat task fills in). All disabled by default.
v0.4.0
  • Self-service portal + admin UI + ServiceNow webhook
  • Asset type, runbook, and standalone-runbook orchestration
  • VDI and Server lifecycle workflows on XenServer/XCP-ng + vSphere
  • SCCM task-sequence integration (NTLM today; Kerberos backlogged)
  • Active Directory user/manager/group lookups via msldap
  • Entra ID portal SSO via MSAL
  • Conditional approval rules with N-of-M quorum support
  • Approval delegations + reminder/escalation Beat tasks
  • SIEM streaming (Splunk HEC, Microsoft Sentinel, generic webhook)
  • External secret management (Vault KV v2, CyberArk CCP)
  • OpenTelemetry tracing, Audit log retention by classification
  • HA Beat (RedBeat distributed lock)
  • RBAC slices 1-3: 5-tier role ladder, per-user accounts, per-asset-type ACL grants, role-bound API tokens, SoD enforcement
Was ist neu in ip·Solis — ip·Solis