Google Git
Sign in
apache/casbin-jcasbin-menu-permission/refs/heads/infrastructure-ruleset-bot/default-branch-protection
commit
c4f4d9c0995d5a19711cf80728021c7a585cad9e
[log]
author
The Apache Software Foundation <root-asf-gitbox-commits@apache.org>
Fri May 15 14:10:20 2026 -0500
committer
The Apache Software Foundation <root-asf-gitbox-commits@apache.org>
Fri May 15 14:10:20 2026 -0500
tree
f51458d8cd0542f51db3ad2f590a05af6f9f76e7
parent
f60130ca95e9e7a5c8cef79bdbdd3611e2ef809d [diff]
Set up default protection ruleset for default and release branches
1 file changed
tree: f51458d8cd0542f51db3ad2f590a05af6f9f76e7
  1. .github/
  2. examples/
  3. src/
  4. .asf.yaml
  5. .gitignore
  6. LICENSE
  7. pom.xml
  8. README.md
README.md

jcasbin-menu-permission

Introduction

This document presents an example of dynamic permission menu loading based on jCasbin. Through jCasbin, you can easily manage menu permissions in Spring Boot development.

Project Overview

Technology Stack

  • Backend: Spring Boot 2.x + jCasbin + Spring Data JPA
  • Frontend: Tailwind CSS + Thymeleaf

Startup Instructions

  1. Build the menu structure you need in the casbin/policy.csv file. Specifically, g2 represents the relationship between menus. For example: g2, submenu name, parent menu name.
  2. Once the configuration is complete, run the main method in Application.java located under org/casbin/. Access http://localhost:8080/ for testing.
  3. The access control model file for jCasbin is located at casbin/model.conf, and the policy file is at casbin/policy.csv. Modify them as needed based on your requirements.

Simple Examples

Demonstration video

Root user

Admin user

Normal user