docs: deepen access (RBAC + ABAC) guide#67
Merged
Merged
Conversation
The flagship authorization guide was the one feature guide left at the old
depth — it explained the code API but never showed how to set RBAC up.
Bring it to the same beginner, step-by-step level as the rest.
- plain-language RBAC vs ABAC intro + a mental-model diagram
(user -> direct/group roles -> permissions; then optional Policy)
- NEW Step 1 "Set up roles & permissions": console + REST tabs with the
verified endpoints — POST /permissions {code,description},
POST /roles {tenantId,code,name},
POST /roles/{id}/permissions/{permissionId} (grant),
POST /roles/{id}/users/{userId} (assign)
- Step 2 PermissionChecker.check + has* (file path)
- Step 3 ABAC Policy bean + PolicyContext.builder + the check overload +
evaluateDetailed + dry-run (kept, framed as a step)
- see-also cross-links
EN + KO. Restored the { #abac-policies } anchor on the (renamed) ABAC
heading so the inbound links from tutorial.md and admin-console.md/.ko.md
still resolve.
Completes the all-guides overhaul: tenancy, access, menus, audit, cache,
bootstrap, config-sync, admin-console.
Verification: mkdocs build --strict clean, no anchor/link warnings.
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
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.
EN
The flagship Access (RBAC + ABAC) guide was the one feature guide still at the old depth — it explained the code API but never showed how to set RBAC up. This brings it to the same beginner, step-by-step level as the rest of the overhaul.
POST /permissions {code, description}POST /roles {tenantId, code, name}POST /roles/{id}/permissions/{permissionId}(grant)POST /roles/{id}/users/{userId}(assign)PermissionChecker.check+has*(with file path)Policybean +PolicyContext.builder+ thecheckoverload +evaluateDetailed+ dry-run (kept, now framed as a step)EN + KO. Restored the
{ #abac-policies }anchor on the renamed ABAC heading so the inbound links fromtutorial.mdandadmin-console.md/.ko.mdstill resolve.This completes the all-guides overhaul: tenancy, access, menus, audit, cache, bootstrap, config-sync, admin-console.
Verification:
mkdocs build --strict— clean, no anchor/link warnings.KO (한국어)
핵심 접근 제어(RBAC + ABAC) 가이드가 유일하게 옛 깊이로 남아 있었습니다 — 코드 API는 설명했지만 RBAC를 설정하는 법은 없었습니다. 전면 개편의 나머지와 같은 초보자용 step-by-step 수준으로 맞췄습니다.
POST /permissions {code, description}POST /roles {tenantId, code, name}POST /roles/{id}/permissions/{permissionId}(부여)POST /roles/{id}/users/{userId}(배정)PermissionChecker.check+has*(파일 경로 포함)Policy빈 +PolicyContext.builder+check오버로드 +evaluateDetailed+ dry-run(유지, 단계로 재구성)한/영. 이름이 바뀐 ABAC 헤딩에
{ #abac-policies }앵커를 복원해tutorial.md·admin-console.md/.ko.md의 인바운드 링크가 계속 동작합니다.이로써 전체 가이드 개편 완료: tenancy, access, menus, audit, cache, bootstrap, config-sync, admin-console.
검증:
mkdocs build --strict— clean, 앵커/링크 경고 없음.