igrantio-credential-schema-authenticator

Provides claim path pointer schemas for issuing iGrant.io Authenticator credentials in three formats.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-authenticator-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-credential-schema-authenticator
Source: https://github.com/L3-iGrant/skills/tree/main/credential-schemas/igrantio-credential-schema-authenticator
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-authenticator-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers integrating passwordless sign-in with EUDI wallets need the exact claim path pointers for the iGrant.io Authenticator credential (io.igrant.authenticator) across dc+sd-jwt, jwt_vc_json, and mso_mdoc formats, and getting these paths wrong breaks credential definitions on the iGrant.io OpenID4VC API. ## Core Features & Use Cases - Ready-to-use claim path documents: Provides the exact claims arrays for all three credential formats, including path, mandatory, and limitDisclosure fields for the single email_address claim. - Credential definition guidance: Shows how to build the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request with correct vct, type, doctype, and validationPath values per format. - Use Case: You are building passwordless sign-in where users present an Authenticator credential instead of a password. Use this Skill to create the credential definition on the iGrant.io API with the correct claim paths, then issue revocable credentials to users. ## Quick Start Use the igrantio authenticator credential schema skill to create a dc+sd-jwt credential definition for io.igrant.authenticator on the iGrant.io demo environment.

Frequently Asked Questions about igrantio-credential-schema-authenticator

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

FAQPage Schema
How do I create an iGrant.io Authenticator credential definition?▼

Call POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with one entry per format in credentialDefinitions. For dc+sd-jwt set vct to io.igrant.authenticator and validationPath to $, copying the claims array from the schema document.

What claims does the io.igrant.authenticator credential contain?▼

The Authenticator credential holds exactly one claim, email_address, which is mandatory in all three formats. It proves control of one email address and is used for passwordless sign-in.

What is the claim path for email_address in each credential format?▼

For dc+sd-jwt the path is ["email_address"], for jwt_vc_json it is ["credentialSubject", "email_address"], and for mso_mdoc it is ["io.igrant.authenticator", "email_address"] using the mDoc namespace prefix.

Does jwt_vc_json support selective disclosure for this credential?▼

No, jwt_vc_json has no selective disclosure, so its claim path document omits the limitDisclosure field. The dc+sd-jwt and mso_mdoc documents set limitDisclosure to true for the email_address claim.

Should the Authenticator credential support revocation?▼

Yes, a sign-in credential must be revocable, so set supportRevocation to true with revocationMethod status_list when creating the credential definition. This applies to any credential with a lifetime.