Skip to content

WaboSign 1.0.0

Choose a tag to compare

@wabolabs wabolabs released this 17 May 19:09
· 134 commits to master since this release

First WaboSign release. Forked from DocuSeal 2.5.3.

Added

  • Google Workspace SSO via omniauth-google-oauth2, configurable from /settings/sso with ENV + DB fallback. See GOOGLE_SSO.md.
  • SMS invitations via BulkVS, configurable from /settings/sms. See SMS.md.
  • Custom account logo upload with server-side SVG sanitization. The logo renders on the sign-in page, signing flow, dashboard navbar, share-link QR page, and audit-trail PDFs.
  • Editor and Viewer user roles alongside Admin. Editors get CRUD on templates and submissions; Viewers get read-only access. Self-service profile management is preserved for every role.
  • OCI image labels (org.opencontainers.image.*) and multi-arch (linux/amd64 + linux/arm64) Docker builds wired via .github/workflows/docker.yml.
  • CHANGELOG.md and a Releases section in README.md.

Changed

  • Removed the upstream "Pro" feature paywall — multi-account, SSO, SMS, audit trail, and timestamping all work out of the box on a self-hosted deployment.
  • Rebranded all UI surfaces, emails, and asset paths from DocuSeal to WaboSign while preserving AGPL §7(b) upstream attribution in NOTICE, REBRANDING.md, LICENSE_ADDITIONAL_TERMS, and the in-app "Powered by" footer.
  • Default container image is now ghcr.io/wabolabs/wabosign (public).
  • Security contact in SECURITY.md now routes to wabosign@wabo.cc.

Removed

  • Developer Newsletter step from the initial-setup flow (was a DocuSeal mailing-list signup).
  • Console-redirect endpoints (/upgrade, /manage, /console_redirect) and the enquiries form — only made sense for DocuSeal's hosted multitenant SaaS.
  • Upstream API-docs language stubs at docs/api/ (10 files referencing api.docuseal.com). The OpenAPI spec at docs/openapi.json and the embedding/webhook guides remain (URLs rewritten to sign.wabo.cc).
  • The "Upgrade to Pro" fallback markup served by the embed-script controller — replaced with a neutral "embed assets not loaded" message.

Security

  • Account-logo SVG uploads are sanitized via Nokogiri before storage (strips <script>, <foreignObject>, on* attributes, and external href / xlink:href values).