Skip to main content

Uni-Verein 1.7.0 – Self-Enrollment for New Members 📝

· 2 min read
René Herrmann
René Herrmann
Senior developer

Published on September 5, 2026

Uni-Verein 1.7.0 makes onboarding new members easier: prospective members can now sign themselves up through a public form, no account needed. This release also ships important security updates for a couple of dependencies.

New Features​

  • 📝 Self-enrollment: A new, publicly reachable form lets prospective members sign themselves up as a member, no account required
  • 🔒 Server-enforced hidden fields: Data that only users may set or that is assigned automatically (task within the club, date fields, SEPA consent) is hidden from the public form and enforced server-side
  • 🚫 Duplicate checks: Email address and IBAN are checked for duplicates just like when an user creates a member, and rejected on a match
  • 🔗 "Self-enrollment" toggle: A new setting in the general club settings that turns the public form on or off, including a button to directly share the link

Improvements​

  • 🧩 Member-creation logic was consolidated into a shared MemberService.CreateMemberAsync instead of being duplicated between user creation and self-enrollment
  • 🧩 Recurring EF Core queries were unified behind a new ReferenceDataService
  • 🌐 frontend/nginx.conf now serves the SPA with a try_files fallback to index.html

Security​

  • 🔐 Updated the fast-uri and @tiptap/* dependencies, closing four High-severity SSRF/host-confusion advisories and one Moderate-severity prototype-pollution-to-XSS advisory

Why These Updates Matter​

Self-enrollment takes a lot of manual work off a club board's plate: instead of creating every new member one by one, you simply share the form's link and prospective members enter their own details. Server-enforced fields and the duplicate checks keep data quality on par with an admin-created member. The security updates also close known vulnerabilities in dependencies the project relies on.

What's Next?​

As always, feedback and feature requests are very welcome via GitHub Issues. Check back here again soon!