External Idp Integration
Enforce MCP server integration with external centralized identity providers. Use when building, configuring, or reviewing MCP server authentication against external IdPs like Keycloak.
Install
$ agentstack add skill-redhatproductsecurity-prodsec-skills-external-idp-integration ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-redhatproductsecurity-prodsec-skills-external-idp-integration) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
External IdP Integration for MCP Servers
Security Requirement
MCP servers MUST be capable of integrating with centralized identity providers (e.g., Keycloak) for authentication and authorization. The MCP server should not implement its own user store but delegate identity management to an external IdP.
Why External IdP
| Benefit | Description | |---|---| | Centralized identity | Single source of truth for user and service identities | | Standard protocols | OIDC/OAuth 2.1 compliance out of the box | | Enterprise features | MFA, federation, session management handled by IdP | | Reduced attack surface | MCP server does not store credentials | | Consistent policy | Same authentication policies across all services |
Integration Requirements
The MCP server must:
- Discover the IdP via standard metadata endpoints (
/.well-known/openid-configurationor/.well-known/oauth-authorization-server) - Validate tokens issued by the IdP (JWT signature verification against JWKS)
- Accept tokens from the configured IdP(s) only
- Allow configuration of the trusted IdP issuer URL
Example Configuration
auth:
idp:
issuer: "https://keycloak.example.com/realms/mcp"
jwks_uri: "https://keycloak.example.com/realms/mcp/protocol/openid-connect/certs"
audience: "mcp-server"
require_auth: trueImplementation Checklist
- [ ] Support configuring one or more external IdP issuer URLs
- [ ] Discover IdP endpoints via standard metadata (OIDC Discovery or RFC 8414)
- [ ] Validate JWT tokens against the IdP's JWKS endpoint
- [ ] Verify
iss,aud,exp, andscopeclaims on every request - [ ] Reject tokens from untrusted issuers
- [ ] Support Keycloak and other standard OIDC-compliant IdPs
- [ ] Do not implement a built-in user store; delegate to the external IdP
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: RedHatProductSecurity
- Source: RedHatProductSecurity/prodsec-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.