toolframe-oidc-auth 0.2.0__tar.gz

toolframe_oidc_auth-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: Validate Python distribution
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+  workflow_call:
+
+permissions:
+  contents: read
+
+jobs:
+  validate:
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 25
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-24.04, macos-15]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+      - uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+        with:
+          version: '0.12.8'
+          enable-cache: false
+      - name: Test and install wheel and source distribution
+        run: python scripts/validate_release.py --output dist/validated
+      - name: Retain only validated distributions
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: python-dist-${{ matrix.os }}
+          path: dist/validated/*
+          if-no-files-found: error
+          retention-days: 14

toolframe_oidc_auth-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,65 @@
+name: Publish Python distribution
+
+on:
+  workflow_dispatch:
+    inputs:
+      index:
+        description: Package index; run against the matching vVERSION tag
+        type: choice
+        options: [testpypi, pypi]
+        default: testpypi
+        required: true
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-${{ inputs.index }}
+  cancel-in-progress: false
+
+jobs:
+  release-tag:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+      - name: Require the exact package version tag
+        env:
+          RELEASE_REF: ${{ github.ref }}
+        run: |
+          python - <<'PYCODE'
+          import os, pathlib, tomllib
+          project = tomllib.loads(pathlib.Path('pyproject.toml').read_text())['project']
+          expected = 'refs/tags/v' + project['version']
+          if os.environ['RELEASE_REF'] != expected:
+              raise SystemExit('Publication requires ' + expected)
+          PYCODE
+
+  validate:
+    needs: release-tag
+    uses: ./.github/workflows/ci.yml
+    secrets: inherit
+
+  publish:
+    needs: [release-tag, validate]
+    runs-on: ubuntu-24.04
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.index }}
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: python-dist-ubuntu-24.04
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          packages-dir: dist/
+          repository-url: ${{ inputs.index == 'testpypi' && 'https://test.pypi.org/legacy/' || 'https://upload.pypi.org/legacy/' }}

toolframe_oidc_auth-0.2.0/.gitignore

@@ -0,0 +1,15 @@
+/.venv/
+/dist/
+/build/
+/.pytest_cache/
+/.ruff_cache/
+__pycache__/
+*.py[cod]
+/examples/tinyauth/.env
+/examples/tinyauth/secrets/
+/examples/tinyauth/certs/
+
+# Local working documents, issue state, and development worktrees.
+/.local/
+/.issues/
+/.worktrees/

toolframe_oidc_auth-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

toolframe_oidc_auth-0.2.0/NOTICE

@@ -0,0 +1,2 @@
+toolframe-oidc-auth
+Copyright 2026 byfb

toolframe_oidc_auth-0.2.0/PKG-INFO

@@ -0,0 +1,235 @@
+Metadata-Version: 2.5
+Name: toolframe-oidc-auth
+Version: 0.2.0
+Summary: Shared OIDC sign-in and OAuth delegation for Toolframe
+Project-URL: Homepage, https://github.com/toolframe/toolframe-oidc-auth
+Project-URL: Repository, https://github.com/toolframe/toolframe-oidc-auth
+Project-URL: Documentation, https://github.com/toolframe/toolframe-oidc-auth#readme
+Project-URL: Issues, https://github.com/toolframe/toolframe-oidc-auth/issues
+Author-email: byfb <62798989+byfb@users.noreply.github.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.14
+Requires-Dist: authlib==1.8.0
+Requires-Dist: cryptography==50.0.2
+Requires-Dist: httpx2<3,>=2.8
+Requires-Dist: starlette<2,>=1
+Requires-Dist: toolframe-sdk==0.3.0
+Description-Content-Type: text/markdown
+
+# Toolframe OIDC Auth
+
+Use one OIDC identity for Dashboard sign-in and separate, revocable OAuth grants
+for third-party agents. Authlib implements the upstream OIDC client and downstream
+OAuth authorization server. Toolframe Auth owns local users, browser sessions and
+permission grants; MCP Auth consumes the shared token-verification service.
+
+This plugin requires SDK 0.3.0, Core 0.6.1, Auth 0.2.0, Dashboard Auth 0.1.3 and
+MCP Auth 0.2.0.
+The OIDC plugin is optional and is not enabled by the Entry Register template.
+
+## Quick start
+
+1. Add the package to a running application, leaving it disabled until configured:
+   `toolframe --home APP plugin add pypi:toolframe-oidc-auth==0.2.0`.
+2. Install compatible Core, Auth and Dashboard packages. For an existing Auth v1
+   store, back it up with its retained secrets, stage the new Auth wheel with
+   `toolframe --home APP plugin update auth --source pypi:toolframe-auth==0.2.0`, inspect
+   `toolframe --home APP migrate plan auth`, then apply that returned plan using
+   `toolframe --home APP migrate apply auth --plan-id PLAN_ID`. Migration v2 only
+   adds user, external-identity, session and agent-grant tables.
+3. Register a confidential web client at the upstream identity provider, with
+   the exact callback `https://app.example/_toolframe/oidc/callback/google`.
+   Store its client secret in a regular file readable only by the application
+   owner (`chmod 600`); use an absolute path in configuration.
+4. Add the following desired-state settings to `APP/toolframe.toml`, preserving
+   the application's existing ID, plugin declarations and storage configuration.
+   Replace example values, then run `toolframe --home APP apply`.
+
+```toml
+[application]
+# Keep the existing application ID and other settings.
+public_url = "https://app.example"
+
+[access]
+mode = "protected"
+failure_mode = "closed"
+auth_provider = "auth"
+dashboard_auth = "dashboard-auth"
+oidc_provider = "oidc-auth"
+
+[mcp_access]
+mode = "protected"
+auth_provider = "mcp-auth"
+
+[plugins.auth.config]
+identity_provider = "oidc-auth"
+federated_identities = [
+  { issuer = "https://accounts.google.com", subject = "VERIFIED_GOOGLE_SUB", label = "Alice", scopes = ["entry-register.read"] },
+]
+
+[plugins.oidc-auth]
+source = "pypi:toolframe-oidc-auth==0.2.0"
+enabled = true
+
+[plugins.oidc-auth.config]
+public_url = "https://app.example"
+scopes = ["entry-register.read"]
+dynamic_registration = true
+max_clients = 1000
+access_token_seconds = 300
+grant_seconds = 2592000
+
+[plugins.oidc-auth.config.providers.google]
+label = "Google"
+issuer = "https://accounts.google.com"
+server_metadata_url = "https://accounts.google.com/.well-known/openid-configuration"
+client_id = "GOOGLE_CLIENT_ID"
+client_secret_file = "/absolute/private/google-client-secret"
+```
+
+The `auth`, `dashboard-auth`, `mcp-auth` and SQLite provider must be enabled in the
+existing composition. Set Core's `application.public_url` and this plugin's
+`public_url` identically. Terminate HTTPS at a reverse proxy and preserve the
+canonical Host. Core never derives its issuer from forwarded headers. Only
+explicit OAuth routes allow cross-origin entry; Dashboard management and consent
+submission remain same-origin. Public-host requests cannot inherit proxy-loopback
+operator privileges. Configure proxy request limits for publicly exposed login
+and dynamic-registration endpoints.
+
+The login page offers **Continue with Google** alongside Access Password login.
+Admission uses an administrator-verified **issuer + subject**, never an email
+address. The allowlist creates a local user on first successful login. Later
+changes belong to **User access** or the protected user-management API; changing
+that initial-admission entry does not overwrite an existing user. Unlisted
+identities are rejected. A user needs the relevant business scopes before they
+can delegate them to an agent. `system.auth.users` grants scoped user management;
+each federated user receives `system.auth.self` for their own connections.
+
+## Google, Keycloak and TinyAuth
+
+Upstream providers share the same Authlib adapter; they do not need separate
+Toolframe authentication implementations. Use Keycloak as an identity broker by
+setting its realm issuer and discovery URL and registering the same Toolframe
+callback under a chosen provider ID, for example `keycloak`. Google can then be
+configured as an upstream provider within Keycloak. Toolframe still owns local
+permissions and issues the app-specific access token.
+
+Each provider accepts `issuer`, `server_metadata_url`, `client_id`,
+`client_secret_file`, optional `label`, optional `ca_file`, and
+`token_endpoint_auth_method` (`client_secret_basic`, the default, or
+`client_secret_post`). HTTPS certificate validation stays enabled. `ca_file` adds
+a private CA for a controlled deployment; client secrets and IdP tokens are never
+included in browser presentation or the configuration journal. A changed secret
+file requires plugin reload. Provider metadata is discovered lazily, so an IdP
+outage does not prevent plugin startup or invalidate existing local sessions.
+
+See the [TinyAuth Docker fixture](examples/tinyauth/README.md) for reproducible,
+local TLS, user and client provisioning. Real acceptance covers TinyAuth; Google
+and Keycloak use the documented generic path but need deployment-specific live
+verification. [Google OIDC documentation](https://developers.google.com/identity/openid-connect/openid-connect),
+[Keycloak identity brokering](https://www.keycloak.org/docs/latest/server_admin/index.html#_identity_broker),
+[Authlib Starlette OIDC client](https://docs.authlib.org/en/latest/client/starlette.html)
+and [Authlib authorization server](https://docs.authlib.org/en/latest/oauth2/server.html)
+describe the upstream protocols and library integration.
+
+## Connect an agent
+
+Give an OAuth-capable MCP client `https://app.example/mcp`. A protected request
+returns a Bearer challenge pointing at protected-resource metadata. The client
+can discover the authorization server, register, request consent and exchange an
+authorization code using PKCE S256. Consent displays the client ID, name, redirect
+URI, target resource and requested scopes; display names are unverified client
+metadata. If necessary, the user signs in at the upstream provider. Dashboard
+and Agent flows resolve to the same local user, with independent credentials.
+
+OAuth endpoints are `/oauth/authorize`, `/oauth/token`, `/oauth/register` (when
+enabled) and `/oauth/revoke`. Authorization-server metadata is
+`/.well-known/oauth-authorization-server/oauth`; resource metadata is
+`/.well-known/oauth-protected-resource/mcp`. Both authorization and token requests
+must include `resource=https://app.example/mcp`. This is the default allowed
+resource; `resources` can declare additional exact URLs for custom consumers of
+the generic verifier. Core currently integrates that verifier with MCP only.
+
+This release supports public clients, authorization-code + S256, refresh-token
+rotation, static registration and bounded RFC 7591 dynamic registration. An
+omitted registration authentication method selects `none`, explicitly returned
+in the registration response. Explicit secret-based client authentication is
+rejected. No wildcard redirects are accepted: redirects must exactly match an
+HTTPS URL or an HTTP loopback URL. To disable DCR, use:
+
+```toml
+[plugins.oidc-auth.config]
+# Include the other required settings from above.
+dynamic_registration = false
+clients = [
+  { client_id = "desktop-agent", client_name = "Desktop agent", redirect_uris = ["http://127.0.0.1:8347/callback"] },
+]
+```
+
+Advertise only the business scopes you intend to expose through this issuer.
+Some MCP clients request every scope in resource metadata. Consent always shows
+the actual requested set. System permissions cannot be delegated. Client ID
+Metadata Documents (CIMD), confidential downstream clients, device grants,
+client-credentials grants, SAML, downstream OIDC ID tokens and automatic
+account linking are outside this release. An upstream ID/access token is never
+accepted as an app bearer token. Existing `tf_mcp_` keys remain usable alongside
+OAuth; an unavailable optional OAuth plugin does not disable key verification.
+
+## Credentials, revocation and backup
+
+OAuth access tokens last 300 seconds by default (30–900 configurable); grants
+last 30 days by default (60 seconds–one year configurable). Tokens use 256 random
+bits and only digests are persisted. Codes expire after 60 seconds and are single
+use. Refresh tokens rotate, cannot outlive the grant, and replay revokes the
+whole grant. Every MCP admission checks token expiry, resource binding, current
+user permissions and grant status. Already admitted operations may finish.
+
+**Connected agents** lets the user revoke a connection without signing out of
+Dashboard. Disabling the user invalidates sessions and revokes all their grants.
+Logout ends the local browser session; it does not globally log out the IdP or
+revoke agent grants. Permission reductions take effect on subsequent admissions.
+OAuth authorization is explicit on each new flow; there is no implicit consent
+based solely on an upstream login.
+
+The plugin persists encrypted, browser-bound ten-minute authorization flows and
+code/token digests in its managed store. Pending flows are capped at 1000 and
+expired flows are removed when new flows are created. Client registrations are
+persistent and bounded by `max_clients`; they are not automatically deleted.
+Token and grant history currently requires operator-managed retention. Back up
+`data/plugins/auth/data.sqlite`, `data/plugins/oidc-auth/data.sqlite`, retained
+`.toolframe/secrets/`, composition, and referenced upstream secret files together,
+using consistent SQLite backups. Keep the `oidc-auth/flow-key.key` secret across
+reloads/restarts. A missing key with an existing store blocks activation; restore it from backup.
+
+## Development checks
+
+With matching SDK, Auth and SQLite packages installed in a Python 3.14 venv:
+
+```sh
+uv pip install --python .venv/bin/python --find-links ../wheelhouse -e .
+uv pip install --python .venv/bin/python pytest pytest-asyncio ruff
+.venv/bin/pytest -q
+.venv/bin/ruff check src tests examples
+```
+
+Tests use real managed SQLite and Authlib grants. They cover PKCE rejection,
+resource binding, one-use codes, refresh rotation/replay, browser-bound consent,
+explicit denial, client registration and revocation. Core's coordinated suite
+covers real workers, discovery, proxy authority and optional-provider outages;
+the fixture script exercises an installed app through real FastMCP OAuth.
+
+For release validation and Trusted Publisher setup, see [releasing](docs/releasing.md).
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+## PostgreSQL storage
+
+Version 0.2 requires SDK 0.3 and declares PostgreSQL migration SQL alongside the
+unchanged SQLite history. Provision this plugin’s stable store owner with the
+PostgreSQL provider before enabling it. The application still runs one Core;
+retain its private keys and configuration with the application home. Existing
+SQLite records are not imported automatically.