261102_01_ENH: 프로젝트 접근 권한 확인 API 추가 및 공통 사용자 Context 적용

This commit is contained in:
2026-11-02 15:12:58 +09:00
parent 9bf9cbe135
commit 32b3d374a3
16 changed files with 168 additions and 21 deletions

View File

@@ -1,6 +1,6 @@
## KART Server Repository Rules
- Java 17, Spring Boot 3.5.7, KriCommon `com.kri.common:starter:beta.1.6.9`.
- Java 17, Spring Boot 3.5.7, KriCommon `com.kri.common:starter:beta.1.7.1`.
- Use MyBatis with explicit KON, KONKIWI and kart (Report DB) SQL Server sessions and transaction managers. Do not infer a source from pkey alone.
- ProjectType codes are 0=KON and 1=KIWI; reject unsupported types and legacy key markers in new project identifiers.
- This API is for the new system. Legacy API compatibility is not required; shared database compatibility is required.
@@ -30,6 +30,7 @@
- Follow Contact: inject com.kri.common.feature.web.RequestUserContext ctx into controller methods; use ctx.getUserRole() and ctx.getUserTeam() for authorization and pass them to the service as needed.
- Use only the context resolved by common authentication, never role/team fields submitted in request DTOs.
- Place Spring MVC interceptors under the interceptor package. Inject KriCommon RequestUserContextProvider to resolve request identity; keep project and share-link authorization policies in KART.
- Do not introduce separate PrincipalKind/ProjectPermission/ReportPage enums or generic grant models for this purpose.
- External authentication must still enforce its stored project/page scope and restrict access to report reads and aggregate Excel; role/team alone must not authorize access outside the link scope.