-
v0.1.0 — Experimental Pre-release
released this
2026-09-27 16:39:46 +02:00 | 4 commits to main since this releasev0.1.0 — experimental first release
2026-09-27. Public source and npm-installable tarball on
Forgejo.
This is an experimental release, not a general production-readiness claim.
The npm publication guard remainsprivate: true; own-code license isUNLICENSED.
Public visibility does not grant open-source reuse rights. No npm-registry release
or production deployment is part of this publication.Included
Existing-account OIDC linking/login, native logout/password fallback, owner-only
embedded Settings, encrypted UI-managed providers, file-managed configuration,
draft/test/activation, and provider-specific sign-in text/icons. See the
changelog and installation guide.Compatibility and known limits
- Exactly n8n 2.27.4, Node >=22.22, Linux/macOS file semantics, one main.
- Historical scoped real Authelia 4.39.28 flow passed; this release
must not claim a new personal MFA test on the basis of that earlier artifact. - Keycloak/ZITADEL are targets, not real-client-qualified integrations. Docker
recipe is illustrative; full core T01–T15 and security review remain incomplete. - Native login is retained. No auto-signup/email merging, role mapping, SCIM,
SAML, single logout, multi-main coordination, key rotation or unlink UI. - Disabling a provider stops new/pending SSO, not existing native sessions.
The validation summary distinguishes historical evidence from
release checks. Do not use this release where those limits are unacceptable.Install the reviewed download
Download the exact
.tgzand checksum assets from the release page. Verify SHA-256,
review the licensing limitation above, then install:npm install --prefix /opt/oidc-bridge --omit=dev --ignore-scripts \ /absolute/path/n8n-oidc-bridge-0.1.0.tgzThis installs the bridge, not n8n. Configure the external hooks, protected bootstrap
and persistent storage using installation. It is not installed
through n8n's Community Nodes menu. Do not upload raw client secrets or private
database files with the release.Upgrading from the development prototype
No application-state migration is introduced by this release preparation. Keep
the same private data directory, UI encryption key and provider/link state. Record
the previous exact artifact and review restart scope. Do not restore an old native
database for a code rollback. Pending flows/grants may need restarting after an
application restart; native password fallback must remain usable.Publication checklist
See distribution for checksums, source/tag handling,
remaining licensing decisions and npm-specific requirements. Local packaging
commands never upload, tag, deploy or publish by themselves.Verified artifacts
73 backend/release tests and 51 browser tests passed. The final tarball passed the isolated native n8n 2.27.4 linking/login/logout/fallback and restart flow. See the attached verification report for exact scope and earlier UI evidence. No fresh real-provider qualification or production deployment is implied.
Download the
.tgz,release-notes.md,package-verification.jsonandSHA256SUMStogether; verify withsha256sum -c SHA256SUMS(Linux) orshasum -a 256 -c SHA256SUMS(macOS). The test report has its owntest-verification.sha256.Tarball SHA-256:
3447ef7e7478ce75bf93f590781c2282f3538345fc0d0b4af254bae3df19be83.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads