Affinidi Iota Framework Configuration

To enable Affinidi Iota Framework on your website, you must create an Affinidi Iota Framework configuration where you select the wallet used to sign the request token and the expiration of the request token, including the Presentation Definition to use to query the data from Vault.

Configuration Details

Below are the relevant fields when managing Affinidi Iota Framework Configuration:

Required Fields

• Name of configuration: Assigns name for the configuration for your personal convenience.

• Signing Wallet: Assigns existing wallet or initiates new wallet creation process. Required for signing request token, for initiating data requests from the Affinidi Vault.

  In case you want to create new wallet:

  • Name of Wallet: (Required) Provides name for the new wallet.

  • Description: (Optional) Provides the explanation of wallet usage.

  • DID method of wallet: (Default) By default the new wallet will have the DID method did:key.

  Read more about Wallets here.

• Data sharing flow mode: Affinidi Iota Framework provides different modes of enabling consent-drive data-sharing flow on your applications. Select the option on how you want to handle the data-sharing request. More about this mode here.

• Redirect URLs: Choosing Redirect mode, list the allowed Redirect URLs for user redirection and sending the response from Afiinidi Vault.

• Lifetime of Request Token: Credential Offers have a limited lifetime to enhance security. Consumers must claim the offer within this timeframe.

Optional Fields

• Description: Provides description of the configuration purpose and usage.

• Display name: Name of the configuration displayed on the Affinidi Vault during the process of requesting consent from the consumer.

• Origin: Domain URL displayed on the Affinidi Vault during the process of requesting consent from the consumer.

• Logo URL: Your application’s logo displayed on the Affinidi Vault during the process of requesting consent from the consumer.

Recommended Fields

• Enable Credential Verification: To verify the credentials the user shares using the Credential Verification service.

• Enable Consent Audit Log: To store the consent given by the user whenever they share data with the website.

Identity Verification Flow

• Enable Identity Verification (IDV): When requesting the verified identity VC of the user from their Affinidi Vault is not available, enabling this option triggers the verification process where the user is asked to provide a self-photo and one of the supported documents to verify their identity. You can read more about Identity Verification here.

  The data sharing flow must be in Redirect mode if this option is enabled. You must also create a Presentation Definition to query the verified identity VC from the user’s Affinidi Vault. Refer to this document for details of the query.

Create Affinidi Iota Framework Configuration

You can easily do this using the Affinidi Portal:

1. Go to  Affinidi Portal and click on the Affinidi Iota Framework page.

2. Click on Create Configuration and set the following fields:

3. After setting the fields, including the Wallet used for signing and additional options, click Create.

4. After creating the configuration, define the Presentation Definitions to query specific data from the Affinidi Vault. We will define the Presentation Definition from the Presentation Exchange protocol to do this.

5. Provide the name of the Presentation Definition and then select from the available templates to pre-populate the editor. You can modify the presentation definition template based on the required data you would like to request from the Affinidi Vault.

Click on the + Add button to create additional presentation definitions for the current configuration. After adding the presentation definitions, click on the Create button.

Each Presentation Definition created will have a corresponding Query ID. The Query ID is used to get the presentation definition required to generate the request token to request data from the Affinidi Vault.