custom-claims

Map and inject custom claims into ID tokens during OAuth2 authentication.

7|1|Updated Feb 12, 2023
One-click install
npx skills add https://github.com/hirokazu-kobayashi-koba-hiro/idp-server --skill custom-claims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-claims
Source: https://github.com/hirokazu-kobayashi-koba-hiro/idp-server/tree/main/.claude/skills/custom-claims
Command: npx skills add https://github.com/hirokazu-kobayashi-koba-hiro/idp-server --skill custom-claims

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Custom claims enable embedding user attributes into ID tokens by defining scope-based and verified-claims mappings, reducing custom integration work and ensuring consistent identity data in tokens.

Core Features & Use Cases

  • Scope mapping: claims:attribute_name to add specific attributes to ID tokens.
  • Verified Claims: verified_claims:attribute_name to include verified user data per OIDC4IDA.
  • Usage Example: Map a user's department and identity verification status into the ID token for access decisions.

Quick Start

Configure and validate custom-claims mappings in the ID token generation workflow for a sample user.

Frequently Asked Questions about custom-claims

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map custom claims into an OpenID Connect ID token?

To map custom claims into an OpenID Connect ID token, configure scope-based mappings using the claims:attribute_name syntax. This injects specific user attributes directly into the ID token during the authentication workflow.

What are verified_claims in OIDC and how do I add them to tokens?

Verified_claims in OIDC include verified user data per the OIDC4IDA standard. You add them to tokens by configuring verified_claims:attribute_name mappings to surface identity verification status during token generation.

Can I include user department and identity verification status in an ID token?

Yes, you can include a user's department and identity verification status in an ID token by defining scope-based and verified-claims mappings. This surfaces per-user attributes in tokens for access decisions.

Does custom claims mapping work with OAuth2 implicit and hybrid flows?

Custom claims mapping works with OAuth2 and OpenID Connect deployments across implicit, code, and hybrid flows. It maps per-user attributes into ID tokens regardless of the configured authentication flow.

How do I test custom ID token claims for a sample user?

To test custom ID token claims, configure and validate the claims:attribute_name mappings within the ID token generation workflow for a sample user. This ensures per-user attributes are correctly surfaced before deployment.