Jwt Token Enforcement

Organization

RedHatProductSecurity

jwt-token-enforcement

Enforce short-lived JWT access token validation for inference engines. Use when implementing or reviewing token validation, access control, or request authentication in inference engine endpoints.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`jwt-token-enforcement`
Stars	56
Forks	9
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Jwt Token Enforcement AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/jwt-token-enforcement
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/jwt-token-enforcement

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/jwt-token-enforcement .claude/skills/jwt-token-enforcement

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jwt Token Enforcement in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Jwt Token Enforcement on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Jwt Token Enforcement is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Short-Lived JWT Token Enforcement for Inference Engines

Security Requirement

Inference engines MUST enforce short-lived JWT access tokens with a maximum TTL of 15 minutes. Tokens MUST be validated against the IdP's JWKS endpoint on every request.

Required JWT Claims Validation

Every request to the inference engine must include a JWT with the following validated claims:

json
{
  "iss": "https://your-idp.com",
  "aud": "https://your-engine.com/inference.api",
  "scope": "chat:read inference:write",
  "sub": "user|service-id",
  "exp": "now+15min (maximum)",
  "jti": "unique_id_for_revocation",
  "cnf": "x509-thumbprint"
}

Claim Validation Rules

Claim	Validation Rule
`iss`	MUST match the configured external IdP issuer URL exactly
`aud`	MUST match the inference engine's audience identifier
`scope`	MUST contain the required scopes for the requested operation
`sub`	MUST identify the user or service account making the request
`exp`	MUST be present and no more than 15 minutes from `iat`
`jti`	MUST be unique; check against revocation blacklist
`cnf`	If mTLS is used, MUST match the client certificate thumbprint (sender-constrained token)

Implementation Checklist

Validate JWT signature against IdP JWKS on every request
Reject tokens with exp exceeding 15 minutes from issuance
Verify iss matches the trusted IdP
Verify aud matches the engine's identifier
Check jti against revocation blacklist (Redis or local cache)
Validate scope contains permissions required for the operation
If mTLS enabled, verify cnf claim matches client certificate
Reject tokens missing any required claims

Frequently asked questions

What does the Jwt Token Enforcement AI skill do?

Enforce short-lived JWT access token validation for inference engines. Use when implementing or reviewing token validation, access control, or request authentication in inference engine endpoints.

Why use Jwt Token Enforcement on TypingMind?

Because you install it once and use it with any model. Jwt Token Enforcement is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Jwt Token Enforcement in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/jwt-token-enforcement. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Jwt Token Enforcement?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Jwt Token Enforcement?

As many as you like. As long as a model supports skills, you can use Jwt Token Enforcement with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Jwt Token Enforcement AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Quarkus Patterns

affaan-m

CommunityPopular

Patrones de arquitectura Quarkus 3.x LTS con Camel para mensajería, diseño de API RESTful, servicios CDI, acceso a datos con Panache y procesamiento asíncrono.

Quarkus Security

Buenas prácticas de seguridad en Quarkus para autenticación, autorización, JWT/OIDC, RBAC, validación de entrada, CSRF, gestión de secretos y seguridad de dependencias.

Quarkus Verification

Bucle de verificación para proyectos Quarkus: build, análisis estático, pruebas con cobertura, escaneos de seguridad, compilación nativa y revisión de diff antes del lanzamiento o PR.

Springboot Security

Buenas prácticas de Spring Security para autenticación/autorización, validación, CSRF, secretos, cabeceras, limitación de velocidad y seguridad de dependencias en servicios Java Spring Boot.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Short-Lived JWT Token Enforcement for Inference Engines

Security Requirement

Required JWT Claims Validation

Claim Validation Rules

Implementation Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now