🚀 Integration → Develop: Auto-promotion after CI success#40
Merged
Conversation
- Create V4 Flyway migration with comprehensive authentication schema - Add roles table with granular permissions (ADMIN, USER, MANAGER, READONLY) - Add users table with role-based access control and MCP access flag - Add api_keys table with scoped access and expiration management - Add user_role_history table for complete audit trail of role changes - Include strategic indexes for performance optimization - Insert default roles with appropriate permission arrays - Insert default admin and user accounts with BCrypt password hashing - Add comprehensive constraints and documentation comments Migration successfully tested locally with PostgreSQL. Tables created: roles, users, api_keys, user_role_history Default data: 4 roles, 2 users, 2 history entries
Adds database-managed user authentication with roles, API keys, and audit trails. - Implements Flyway migration V4 for user management tables. - Enhances security with BCrypt password hashing. - Introduces granular role-based access control (ADMIN, USER, MANAGER, READONLY). - Adds API key management with expiration and usage tracking. - Includes audit trail for role changes.
…on system - Update API reference with database-managed users and 4-role system (ADMIN/MANAGER/USER/READONLY) - Update getting started guide with new authentication examples and BCrypt explanation - Update architecture documentation with enhanced role-based access control - Apply code formatting to SecurityConfig.java per Spotless standards This completes the documentation requirements for task-1: Database Schema Design & Migration. All docs now reflect the transition from hardcoded to database-managed authentication. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…tices BREAKING CHANGE: V4 migration now schema-only, data seeding moved to application bootstrap - Remove all data seeding from V4 migration (users, roles, history) - Keep only schema creation: tables, indexes, constraints, comments - Eliminate hardcoded credentials from version control for security - Delegate user/role management to application bootstrap service (task-14) - Update documentation to reflect new bootstrap-required approach - Follow enterprise migration best practices: schema evolution vs business data separation Security improvements: - No default users with known credentials in production - No passwords visible in version control - Environment-specific user setup through secure bootstrap process Architecture improvements: - Clean separation between schema migrations and data management - Proper delegation to application-level user management - Production-ready security practices 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Removes the docker-compose file for the stage environment. The stage environment is no longer needed, so its corresponding docker-compose file is being removed to streamline the project and avoid unnecessary configuration.
Creates a configuration file to manage backlog settings. - Defines project name, default status, and available statuses. - Configures labels, milestones, and date format. - Sets default port and various operational flags.
…ers-roles-apikeys feat: add database schema for users, roles, and API keys
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Automated Promotion from Integration
This PR was automatically created after successful CI validation on the integration branch.
✅ Validation Summary
📋 Changes
🔗 CI Details
🚀 Next Steps
This PR was automatically created by the Integration CI workflow