jinomdeveloper/jinom-token-management
Composer 安装命令:
composer require jinomdeveloper/jinom-token-management
包简介
Laravel SDK for Keycloak token management - store, refresh, and introspect OAuth tokens
README 文档
README
Laravel package for Keycloak token management - store, refresh, introspect, and manage OAuth tokens. Supports both User tokens (Authorization Code Flow) and Client tokens (Client Credentials Flow).
Installation
composer require jinom/keycloak-sdk
Publish the config file:
php artisan vendor:publish --tag="keycloak-config"
Configuration
Add these environment variables to your .env:
KEYCLOAK_BASE_URL=https://your-keycloak-server.com KEYCLOAK_REALM=your-realm KEYCLOAK_CLIENT_ID=your-client-id KEYCLOAK_CLIENT_SECRET=your-client-secret # Service Account (Client Credentials) - Optional # Falls back to KEYCLOAK_CLIENT_ID/SECRET if not set KEYCLOAK_SERVICE_ACCOUNT_ENABLED=true KEYCLOAK_SERVICE_CLIENT_ID=your-service-client-id KEYCLOAK_SERVICE_CLIENT_SECRET=your-service-client-secret # Token Cache - Optional KEYCLOAK_TOKEN_CACHE_PREFIX=keycloak_tokens KEYCLOAK_TOKEN_CACHE_TTL=2592000 KEYCLOAK_TOKEN_BUFFER_SECONDS=30 KEYCLOAK_CLIENT_TOKEN_TTL=300
Usage
User Token (Authorization Code Flow)
For operations on behalf of a user:
use Jinom\Keycloak\Facades\KeycloakSdk; // Store tokens after OAuth callback KeycloakSdk::storeTokens($userId, [ 'access_token' => $token, 'refresh_token' => $refreshToken, 'expires_in' => 300, ]); // Get a valid token (auto-refreshes if expired) $token = KeycloakSdk::getValidToken($userId); // Check if user has valid tokens if (KeycloakSdk::hasValidTokens($userId)) { // User is authenticated } // Get all token data $tokenData = KeycloakSdk::getTokenData($userId); // Introspect a token $introspection = KeycloakSdk::introspectToken($token); // Clear tokens (e.g., on logout) KeycloakSdk::clearTokens($userId);
Client Token (Client Credentials Flow)
For service-to-service communication without user context:
use Jinom\Keycloak\Facades\KeycloakSdk; // Get client token for system operations $clientToken = KeycloakSdk::getClientToken(); // Use for API calls Http::withToken($clientToken)->get('https://api.example.com/users');
Using Dependency Injection
use Jinom\Keycloak\Contracts\TokenManagerInterface; class MyController extends Controller { public function __construct( private TokenManagerInterface $tokenManager ) {} public function userAction(int $userId) { // User token $token = $this->tokenManager->getValidToken($userId); } public function systemAction() { // Client token $token = $this->tokenManager->getClientToken(); } }
When to Use Which Token?
| Operation | Token Type | Reason |
|---|---|---|
| Check user exists | Client Token | System checking, no user context |
| Create/Register user | Client Token | System provisioning |
| Update user by self | User Token | User changing own data |
| Update user by system | Client Token | System/admin sync |
| Delete user | Client Token | Admin operation |
| Get own profile | User Token | User accessing own data |
| List all users | Client Token | Admin/system operation |
API Reference
| Method | Description |
|---|---|
storeTokens($userId, $tokenData) |
Store tokens from OAuth callback |
getValidToken($userId) |
Get valid user access token (auto-refresh) |
getClientToken() |
Get client token (Client Credentials flow) |
refreshToken($userId, $refreshToken) |
Manually refresh the access token |
clearTokens($userId) |
Clear all tokens for a user |
hasValidTokens($userId) |
Check if user has valid tokens |
getTokenData($userId) |
Get all stored token data |
introspectToken($token) |
Introspect token with Keycloak server |
Keycloak Setup for Client Credentials
- Go to Keycloak Admin Console
- Select your realm
- Go to Clients → Select your client
- Enable Service Account Enabled under Settings
- Add required Service Account Roles under Service Account Roles tab
License
MIT
jinomdeveloper/jinom-token-management 适用场景与选型建议
jinomdeveloper/jinom-token-management 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 37 次下载、GitHub Stars 达 0, 最近一次更新时间为 2026 年 04 月 16 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「oauth」 「laravel」 「keycloak」 「jinomdeveloper」 「token-management」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 jinomdeveloper/jinom-token-management 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 jinomdeveloper/jinom-token-management 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 jinomdeveloper/jinom-token-management 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
WeChat OAuth SDK
Ory-Hydra OAuth 2.0 Client Provider for The PHP League OAuth2-Client
Library for ORCID web services
A lightweight and powerful OAuth 2.0 authorization and resource server library with support for all the core specification grants. This library will allow you to secure your API with OAuth and allow your applications users to approve apps that want to access their data from your API.
Auth package against Keycloak for Saml and Openid-Connect
This package supports Keycloak administrator client API, authenticating with username and password or using the security key (client_secret)
统计信息
- 总下载量: 37
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 35
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2026-04-16