mcpField
O
Oauth2 Authorization Server

Oauth2 Authorization Server

Local
github.com/musabbozkurtDatabases6Updated 3d ago

About Oauth2 Authorization Server

This repository provides a Spring Boot OAuth2 Authorization Server with database, Redis, observability, and AI-related components. Its README documents Docker-based operation, tests, and options for AOT, native images, and checkpoint/restore.

Key features

  1. 01OAuth2 authorization server
  2. 02MariaDB and Redis services
  3. 03Docker Compose setup
  4. 04AOT and native-image build paths
  5. 05CRaC checkpoint and restore
  6. 06Automated dependency update workflow

Use cases

  1. 01Run and test an OAuth2 server locally
  2. 02Inspect API endpoints with Swagger UI
  3. 03Build and run a native image
  4. 04Checkpoint and restore the application

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"oauth2-authorization-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"compose"
]
}
}
}
Run commanddocker run -i --rm compose

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocicompose

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

OAuth2 Authorization Server with Spring Boot 4 and Java 26

Prerequisites
  • Java 26 should be installed --> export JAVA_HOME=$(/usr/libexec/java_home -v 26)
  • Maven should be installed
  • Docker should be installed
  • Postman can be installed
How to Run and Test
  • Run the following commands to set environment variables for AI model API keys

    •   export OPENAI_API_KEY=your_api_key_here
        export DEEPSEEK_API_KEY=your_api_key_here
        export ANTHROPIC_API_KEY=your_api_key_here      # Optional
        export GOOGLE_GENAI_API_KEY=your_api_key_here   # Optional
      
  •   cd oauth2-authorization-server
      
      # Run tests on the host (requires Docker for Testcontainers)
      mvn clean verify
      
      # Build and start the application together with all infrastructure services
      docker compose --profile start_application up -d --build
      
      # Start only infrastructure services (Redis, MariaDB, LDAP, Ollama, etc.)
      docker compose up -d
      
      # For local development without Docker (requires infrastructure services running via docker compose up -d)
      ./mvnw spring-boot:run   # or: mvn spring-boot:run
    
  • Import the followings to test in Postman

  • Swagger: http://localhost:9000/swagger-ui/index.html

    • Click Authorize and enter the following credentials
    • client_id: client
    • client_secret: secret
    • Use one of the following default values to log in http://localhost:9000/login
      • username: Developer password: password
      • username: Admin password: password
      • username: User password: password
  • Actuator: http://localhost:9000/actuator/

  • Database credentials

    • url: jdbc:mariadb://localhost:3306/oauth2_authorization_server
    • username: mb_test
    • password: test
  • Redis

    • host: localhost
    • port: 6379
  • Redis Insight: http://localhost:5540/

    • Click Add Redis database
    • Connection URL --> redis://[email protected]:6379
    • Click Add Database
    • img.png
  • Ollama

    • http://localhost:3000/ sign up for an account for local environment
    • Search for mxbai-embed-large and download it if it does not exist
    • Search for mistral and download it if it does not exist
    • Search for deepseek-r1:7b and download it if it does not exist
  • Grafana UI

Debugging Spring Boot Tests in IntelliJ IDEA
  1. Run one of the below commands in the terminal
    • mvn test -Dmaven.surefire.debug
    • If port 5005 is already in use, you can specify a custom port
      • mvn test -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000"
  2. Open IntelliJ IDEA
  3. Go to Run > Attach to Process (or use shortcut)
    • Windows/Linux: Ctrl + Alt + 5
    • Mac: Cmd + Alt + 5
  4. Select the Java process running your tests
  5. The test will pause until you connect your debugger. Once connected, you can use breakpoints and step through your code.
How to Run and Test with CDC (Class Data Sharing)
  • Java 26+ should be installed
  • Run ./mvnw clean install or./mvnw clean install -Paot or ./mvnw -Paot package command to build the application with AOT
  • Run docker-compose up -d command to run necessary services
  • Run docker build -t oauth2-authorization-server -f DockerfileForAOTCache . command to build the image
  • Run docker run -d --restart=always -p 9000:9000 oauth2-authorization-server:latest command to run the image
How to Run and Test Native Image with GraalVM
  • Java 26 GraalVM edition should be installed
  • Run docker-compose up -d command to run necessary services
  • Run ./mvnw -Pnative native:compile or ./mvnw -Pnative native:compile -DskipTests command to build the native image
  • Run ./target/oauth2-authorization-server command to run the native image
  • Install Grype (OPTIONAL)
    • Run native-image-inspect ./target/oauth2-authorization-server-0.0.1 | grype -v command to scan vulnerabilities
  • Run native-image-inspect ./target/oauth2-authorization-server-0.0.1 >output.json command and open output.json or visit http://localhost:9000/actuator/sbom/native-image to inspect all libraries, methods etc. used in the native image
  • Run open ./target/oauth2-authorization-server-build-report.html to see build report
  • Use Swagger UI to test the application
Spring Boot with CRaC (Coordinated Restore at Checkpoint) by Creating Ready to Restore Container Image.
  • Warning: for real projects make sure to not leak sensitive data in CRaC files since they contain a snapshot of the memory of the running JVM instance.
  • Checkpoint
  • Restore
    • Restore the application with: ./docs/scripts/restore.sh
  • Use Swagger UI to test the application
Docker Compose image versions
  • Check pinned image tags in docker-compose.yml:
    • Linux / macOS / Git Bash: ./docs/scripts/check-compose-image-updates.sh
    • Windows: .\docs\scripts\check-compose-image-updates.cmd
    • Preview upgrades: ./docs/scripts/check-compose-image-updates.sh --dry-run
    • Apply OUTDATED bumps: ./docs/scripts/check-compose-image-updates.sh --apply
  • CI runs the read-only check on every pipeline; automated Maven + Compose upgrades run via .github/workflows/dependency-update.yml.
How to Run and Test AI Models Locally with Docker Desktop Model Runner
  • Requires: Docker Desktop 4.40 and later
  • Run docker-compose up -d command to run necessary services
  • Run docker model pull ai/gemma3:4B-Q4_K_M command to pull the model
    • Run docker model run ai/gemma3:4B-Q4_K_M command to run the model to test it from the command line (OPTIONAL)
  • Docker Desktop --> Settings --> Features in development --> Beta features --> Enable Docker Model Runner --> Enable host-side TCP support --> Apply & Restart
    • Docker_Desktop_Enable_Host_Side_TCP_Support.png
  • Run mvn test or mvn clean install or mvn clean package or ./mvnw clean install command to run all the tests
  • Run mvn spring-boot:run command to run the application
  • Use Swagger UI to test the application
Dependency Version Management

Dependency versions are managed via the Maven Versions Plugin and a version-rules.xml filter that excludes alpha/beta/RC/SNAPSHOT releases.

Local — using the helper script:

./docs/scripts/update-versions.sh check           # Show all outdated versions (parent + props + deps + plugins)
./docs/scripts/update-versions.sh update          # Auto-update everything and review with: git diff pom.xml
./docs/scripts/update-versions.sh update-props    # Update only <properties> versions (safest)
./docs/scripts/update-versions.sh update-parent   # Update only spring-boot-starter-parent
./docs/scripts/update-versions.sh revert          # Revert pom.xml from backup

CI/CD — automated PR creation:

The MB Dependency Version Update workflow runs every Monday (and on-demand), checks for updates, verifies the build compiles, and creates a PR automatically.

References

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.