6 Open Issues Need Help Last updated: Aug 28, 2025

Open Issues Need Help

View All on GitHub

AI Summary: This issue outlines the creation of a small React/TypeScript admin UI using Vite and RTK Query. It will include core features like login, tenant listing, and user management (list/create), with a focus on implementing a secure authentication flow involving token storage and refresh strategy.

Complexity: 3/5
good first issue

AI Summary: This issue aims to establish robust integration tests using Testcontainers for an application's authentication and tenant isolation features on MySQL 8.4. It involves setting up a shared MySQL container, applying migrations and seed data, and then writing comprehensive tests for login, refresh, role-based access, tenant separation, and various token states (expired, early, forged). The goal is to ensure these tests are integrated into CI with visible reports and coverage.

Complexity: 3/5
good first issue

AI Summary: This issue aims to establish a robust database setup using MySQL 8.4 via Docker Compose, with schema management handled by Liquibase. The core task involves seeding specific per-tenant data for development and testing, ensuring the application, Testcontainers, and CI pipeline correctly integrate with these migrations and seeded data.

Complexity: 3/5
good first issue

AI Summary: This issue aims to implement Role-Based Access Control (RBAC) with a defined role hierarchy (ADMIN > MANAGER > USER). It involves configuring a role hierarchy bean, applying `@PreAuthorize` annotations on service methods, and defining endpoint access rules for sample resources. The solution must include comprehensive tests for access control, ensure proper 403 responses for insufficient roles, and update OpenAPI descriptions to reflect role requirements, along with documentation updates.

Complexity: 3/5
good first issue

AI Summary: This issue describes the implementation of a multi-tenant resolver for an application, where each request must operate within a specific tenant scope. It involves creating a `OncePerRequestFilter` to extract `tenant_id` from JWT claims or headers, setting it in a `ThreadLocal TenantContext`, and propagating this context to JPA queries. The system must also enforce tenant presence where required, with comprehensive unit and integration tests, and updated documentation.

Complexity: 3/5
good first issue