Admin authentication and authorization system reference — login flow, JWT, TOTP, sessions, RBAC
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
init_data to Login Backend (:8082)tg_id from init_dataIf admin user has no TOTP configured:
LOGIN_TOTP_SECRET_KEY)Claims:
{
"sub": "admin_user_uuid",
"sid": "session_uuid",
"role": "admin|superadmin|...",
"exp": "...",
"iat": "..."
}
LOGIN_JWT_SECRET (must match ADMIN_WEB_JWT_SECRET in backend)admin_sessions tableADMIN_WEB_SESSION_IDLE_TIMEOUT, default 30m)LOGIN_SESSION_MAX_LIFETIME, default 12h)Location: backend/internal/transport/http/middleware/
Authorization: Bearer <token> headersid claimadmin_sessions tableLocation: backend/internal/app/apiapp/routes.go
Two modes (ADMIN_AUTHZ_MODE):
Permissions are granular: view_metrics, export_data, manage_users, moderate_content, manage_access, manage_settings, etc.
| File | Purpose |
|---|---|
adminpanel/backend/login/ | Login backend service |
backend/internal/services/adminacl/ | Admin ACL service |
backend/internal/repo/postgres/admin_session_repo.go | Session repository |
backend/internal/transport/http/middleware/ | Auth middleware |
adminpanel/frontend/src/admin/ | Frontend auth layer |
adminpanel/frontend/src/lib/adminAuthApi.ts | Auth API client |
adminpanel/frontend/src/pages/LoginPage.tsx | Login UI |
# Login Backend
LOGIN_JWT_SECRET=<shared-with-backend>
LOGIN_TOTP_SECRET_KEY=<base64-32-byte-AES-key>
LOGIN_TELEGRAM_BOT_TOKEN=<telegram-bot-token>
LOGIN_SESSION_IDLE_TIMEOUT=30m
LOGIN_SESSION_MAX_LIFETIME=12h
LOGIN_DEV_MODE=true # enables debug init_data login
# Backend
ADMIN_WEB_JWT_SECRET=<must-match-LOGIN_JWT_SECRET>
ADMIN_WEB_SESSION_IDLE_TIMEOUT=30m
ADMIN_AUTHZ_MODE=dual # or permission_only
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
The English summary is being prepared. Showing the original description.
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
The English summary is being prepared. Showing the original description.
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
The English summary is being prepared. Showing the original description.
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.