reject-api-keys
/reject-api-keys
Reject raw API key authentication in inference engines. Use when designing, reviewing, or auditing authentication mechanisms for inference engines or LLM API endpoints in production environments.
- Author
- redhatproductsecurity ↗
- Repository
- prodsec-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 15.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.07.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Reject raw API key authentication in inference engines. Use when designing, reviewing, or auditing authentication mechanisms for inference engines or LLM API endpoints in production environments.
Original author description
Reject raw API key authentication in inference engines. Use when designing, reviewing, or auditing authentication mechanisms for inference engines or LLM API endpoints in production environments.
How it works
- Security Requirement
- Rationale
- Acceptable Approach for Legacy Interop
- Implementation Checklist
SKILL.md preview
---
name: reject-api-keys
description: Reject raw API key authentication in inference engines. Use when designing, reviewing, or auditing authentication mechanisms for inference engines or LLM API endpoints in production environments.
category: "secure_development"
subcategory: "inference-engine"
---
# Reject Raw API Keys in Inference Engines
## Security Requirement
Inference engines MUST reject raw API keys as an authentication mechanism. If legacy interoperability requires API key support, the inference engine (or an API gateway in front of it) MUST proxy and convert API keys into short-lived IdP-issued tokens before processing the request.
## Rationale
API keys present significant security risks in production:
- Typically long-lived, increasing exposure window if compromised
- Difficult to rotate across distributed systems
- Lack fine-grained scoping and sender binding
- Cannot be revoked instantly without infrastructure support
- Do not carry identity claims needed for audit trails
## Acceptable Approach for Legacy Interop
When legacy systems require API key authentication:
```
Client sends API key
→ API Gateway intercepts
→ Gateway exchanges API key for short-lived IdP token
(via client_credentials or token exchange)
→ Gateway forwards IdP token to inference engine
→ Inference engine validates IdP token (never sees API key)
```
## Implementation Checklist
- [ ] Configure inference engine to reject requests authenticated only with API keys
- [ ] If legacy API key support needed, deploy an API gateway as a proxy
- [ ] Gateway exchanges API keys for short-lived IdP tokens (TTL ≤15min)
- [ ] Map API keys to specific service accounts in the IdP
- [ ] Log API key usage for migration tracking
- [ ] Set a deprecation timeline for API key consumers to migrate to OIDC
Versions
The database has no other skills named reject-api-keys.
Database snapshot: 13.11.2026 · package version b19888db6f67 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90authentication-enforcement
Enforce authentication and authorization at the API gateway for AI systems. Use when designing, building, or reviewing API gateways that front inference engines, LLM APIs, or AI model endpoints. - 100oidc-integration
Enforce OIDC IdP integration for inference engines. Use when designing, building, or reviewing authentication for inference engines, LLM APIs, or AI model serving endpoints. - 100api-authentication-api-keys-hmac-signatures
Use this skill when authenticate external API consumers using cryptographically secure API keys and HMAC signatures. - 100api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors. - 100building-api-authentication
Build secure API authentication systems with OAuth2, JWT, API keys, and session management. Use when implementing secure authentication flows. Trigger with phrases like "build authentication", "add API auth", or "secure the API". - 100building-api-authentication
Build secure API authentication systems with OAuth2, JWT, API keys, and session management. Use when implementing secure authentication flows. Trigger with phrases like "build authentication", "add API auth", or "secure the API".