Skip to content

Latest commit

 

History

History
46 lines (32 loc) · 3.35 KB

README.md

File metadata and controls

46 lines (32 loc) · 3.35 KB

Quality Gate Status Lines of Code Maintainability Rating Security Rating

Shōmei - Fast and Secure Authentication System

Shōmei is a JWT-based authentication package designed to help projects implement authentication quickly, securely, and flexibly. It provides a robust system that supports multiple profiles per account, similar to Netflix, along with advanced permission and role management.

Key Features:

JWT Authentication: Provides secure access tokens for managing user sessions.
Multiple Profile Support: Each account can have multiple profiles, allowing for independent customization and control.
Role and Permission Management: Defines differentiated access according to system requirements.
Enhanced Security: Implements best security practices to protect credentials and user data.
Scalability and Flexibility: Easily integrates with any API or backend service.

Technologies & Patterns Used:

🚀 CQRS (Command Query Responsibility Segregation) for clear separation between queries and commands.
🔄 MediatR for efficient handling of events and commands.
🛠 Entity Framework Core for data persistence.
🔐 FluentValidation for request validation in authentication flows.
📢 Serilog for structured logging and security auditing.

Database Support:

✔️ MySQL (Currently supported)
SQL Server (Coming soon)
PostgreSQL (Coming soon)

Shōmei is the perfect solution for projects that require fast, secure, and highly customizable authentication. 🚀


📖 Documentation & Implementation Guide (if you see this is not ready yet come back 👻)

Check out the full documentation to learn how to implement Shōmei in your project:

🔗 Shōmei Documentation


☕ Buy Me a Coffee

If you found Shōmei useful and would like to support the project, feel free to buy me a coffee!

Note: The license is currently Apache License 2.0, and while we don’t expect it to change anytime soon, who knows what the future holds? (This is just for legal reasons.) We’re not fortune tellers. Future versions might have a different license, but don’t worry—old versions will stick with the license they came with.