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. Presentation request query types

DIDAuth

If Query.type = โ€œDIDAuthโ€ , then it is a basic authentication request that does not include a verifiable credential : there is no selection of credential to propose to the user, call the function didkit.DIDAuth(did, โ€œ{โ€œ challenge โ€:โ€œ โ€ฆ. โ€,โ€œ domain โ€:โ€œ โ€ฆ.. โ€}โ€, key) which will create an empty presentation used only for authentication. The presentation passed with the POST request will look like this:

{
  "@context": [
    "https://www.w3.org/2018/credentials/v1"
  ],
  "type": "VerifiablePresentation",
  "proof": {
    "type": "EcdsaSecp256k1Signature2019",
    "created": "2021-08-28T16:13:23.740Z",
    "challenge": "d602e96d-08cb-11ec-a6fa-8d5c53eaebfb",
    "domain": "talao.co",
    "jws" : "eyJhbGciOiJFUzI1NksiLCJjcml0IjpbImI2NCJdLCJiNjQiOmZhbHNlfQ..PgpEElB1tvcY9tdzK6EDKLvysj3vcH-zg5EIiGpk_q4m0NrAmjA81B7QdVvKllSzzfKw-1oTJuu4b4ihCvMXRwA"
  },
  "holder": "did:ethr:0xee09654eedaa79429f8d216fa51a129db0f72250"
}

If Query.type =โ€QueryByExample โ€œthen it will take the user selects credentials in a list constituted according to the criteria specified in โ€œcredentialQuery.exampleโ€. Then it will be necessary to call the didkit.issuePresentation (โ€ฆ) function as what is currently done (there is no change in the function call).

Refer to https://w3c-ccg.github.io/vp-request-spec/#query-by-example for more information.

PreviousVerifier implementationNextQueryByExample

Last updated 2 years ago

๐Ÿ—‚๏ธ
๐Ÿ”