Altme's documentation
  • 🧾Introduction
    • πŸ“‹What is Self Sovereign Identity ?
    • πŸ•΅οΈAltme solution suite is made up of 3 components
      • πŸ—‚οΈAltme Wallet
      • πŸ“‡Altme Saas
      • πŸ“‡Altme Web3 issuer
    • πŸ—‚οΈGive an Identity to your crypto wallet
    • πŸ› οΈTechnical considerations
  • ☁️Altme Saas
    • Quick start
      • ⬇️Download Altme Wallet from Apple or Google store
      • πŸ“Get more credentials in your wallet
      • πŸ”’Connect to the Altme Saas platform to setup a SSI verifier
      • πŸ“²Integration in your app
    • Beacon integration
      • πŸ–₯️Overview
      • πŸ…Verify the age of your users (+13, +18) in a dApp
      • πŸ“²Receive the Verifier data with a webhook in your backend
      • πŸͺ™On-chain and off-chain access with TezID
      • πŸ’ΎVerify other data with other credentials
      • πŸ“‡Issue a Welcome card in a dApp
      • βœ…Check user data of your Issuer (no code)
      • βœ…Check user data of your Issuer with a webhook
      • πŸ•΅οΈUnder the hood : the process flow of a Beacon Verifier
    • OpenID integration
      • πŸ–₯️Overview
      • 1️Example 1 with an β€œimplicit flow” with no code
      • 1️Example 1 with an β€œauthorization code flow” in Python
    • EBSII integration
  • πŸ—‚οΈAlme Wallet
    • Protocols overview
      • πŸ”‘Collecting a verifiable credential
      • πŸ”‘Requesting a verifiable presentation
    • Credential offer protocol
      • πŸ§˜β€β™€οΈMotivation
      • πŸ“–Issuer implementation
    • πŸ–₯️Credential manifest of the credential offer protocol
    • πŸ’°Wallet rendering
      • πŸ“Input descriptors
    • Presentation request query types
      • πŸ§˜β€β™€οΈMotivation
      • πŸ“–Verifier implementation
      • πŸ”DIDAuth
      • QueryByExample
      • QBE Examples
    • βœ…Issuers and Verifiers return codes accepted by wal
    • πŸ”—Universal link
      • πŸ–₯️Access from a desktop viewer
      • πŸ“±Access from smartphone viewer
  • *️Others
    • πŸ“‚Flow between wallet, dApp and Verifier
      • πŸ“±Hybrid dApp onboards a user with VCs
      • πŸ“±dApp onboards a user with VCs
      • πŸ“±dApp adds a user in whitelist
    • πŸ“Indices and tables
      • πŸ“Index
      • πŸ”Search
    • πŸ‘¨β€πŸ’»Show source
Powered by GitBook
On this page
  1. Alme Wallet
  2. Wallet rendering

Input descriptors

PreviousWallet renderingNextPresentation request query types

Last updated 2 years ago

Input descriptors are used to specify the data or credentials needed to issue a credential. It is a main feature of DIF Presentation Exchange. See for more information.

An example here with only input descriptors (EmailPass required to issue a credential) :

{
"credential_manifest": {
  "presentation_definition": {
    "id": "32f54163-7166-48f1-93d8-ff217bdb0653",
    "input_descriptors": [
      {
        "id": "emailPass_input_1",
        "constraints": {
          "fields": [
            {
              "path": [
                "$.type"
              ],
              "filter": {
                "type": "string",
                "pattern": "EmailPass"
              }
            }
          ]
        }
      }
    ]
  }
  }
}

Example to request any credentials with the attribute birthDate

{
"credential_manifest": {
  "presentation_definition": {
    "id": "32f54163-7166-48f1-93d8-ff217bdb0653",
    "input_descriptors": [
      {
        "id": "#765765",
        "constraints":
          "fields": [
            {
              "path": [
                "$.credentiaSubject.birthDate"
              ]
            }
          ]
        }
      }
    ]
  }
  }
}
πŸ—‚οΈ
πŸ’°
πŸ“
https://identity.foundation/presentation-exchange/#presentation-definition