Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When accessing Gataca Studio, you can create a new issuance template from the main dashboard or click "Create New issuance template " in the issuance templates section.

...

Basic configuration

Issuance ID - Name the issuance template

The first step is to select your issuance template name (Issuance template identifier).

This name will be associated with the issuance process for users and will also serve as a reference to the credential the user is requesting when interacting with your platform.

Example:

...

Requester DID

In some cases, you may need to create a DID first (See the tutorial on creating DIDs).

Verifiable Credentials are associated with a specific DID as the owner or holder of that credential. In an SSI ecosystem, Issuers, Users, and Verifiers are all represented by one or more DIDs. As an issuer, you will have to select the DID you want to associate with this credential.

Example:

Select DID method

This field specifies how to deal with this DID. Computers understand where to fetch the DID when reading this part of the DID. For example, GATACA's DID method is denominated "gatc"

You can select between two different DID methods:

EBSI https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/EBSI+DID+Method

GATACA https://github.com/gataca-io/gataca-did-method

Example:

QR Code viewing duration - How much time should the user view the QR code?

Amount of time that the user has to scan the QR Code, in seconds.

Usually between one and two seconds.

Example:

Consent duration - How much time should my company store and process data shared by users?

Amount of time your company has to store and process data shared by users in days.

According to the GDPR, the storage limitation principles state that you should keep personal data for as long as the purpose is unfulfilled. Once the data has served its purpose, you should then delete it.

However, this goes beyond data just serving its purpose. If you are collecting data and it is just sitting around, you will need to consider deleting it and stop any further collection of that specific data category.

Please check with your corresponding data privacy regulations if your organization is outside the EU.

Example:

Callback

URL of a service that is notified by a post notification with the session data when the session has been validated.

Example:

Service description - What to include in the service description?

Include briefly all relevant information about the service associated with the verifiable credential.

Example:

...

Issuance

Credential Types - How to select the credential type to be issued?

All verifiable credentials must declare their type in their template. The credential type distinguishes a verifiable credentials structure from other credentials, and it ensures interoperability between issuers and verifiers.

Gataca Studio covers a great number of credential types. Nevertheless, new credential types will be added soon.

Depending on the service you provide, select the most appropriate one.

...

Example:

...

Credential Attributes - What credential attributes should be included?

Credential attributes are stored in the authorization credential of a user. These attributes store and contain information about the identity and authorization capability of the subject of the credential.

Select which attributes or information will be contained in the credential that you will be issuing.

...

Example:

...

...

Requirements

...

Add credentials claims - What credentials should I request from the user?

Establish the data you will be requesting from your users in order to issue the credential.

...

Scroll the list and tick those credentials you want to select, or use the search bar on top.

Example:

...

How to select required credentials and optional credentials

From the list of credentials, you will be requesting, select those that will be required or will remain optional.

Required credentials mean that the information is critical to fulfilling the credential issuance. Any other “nice nice-to have“ -have information should be marked as optional.

From the list of credentials that you will be requesting, select those that will be required or will remain optional.

Example:

...

Constraints

Credentials trust level - How to determine which credentials are trusted?

In this section, you will determine the level of trust you require from the requested credentials.

(question) What does this mean?

...

Example:

...

Credential data agreement - How to select the credential purpose

In this section, you will determine the reason why you are requesting the previously established credentials from your users. This will be shown to your users.

(question) Explain list

How to create a custom purpose

...

Example:

...

Security configuration

Select any of the following additional security features from the user in order to issue the credential.

  • Add app authentication

  • Add two-factor authentication

...

Successful configuration

How to add an issuance template to the API key

Once you reach the end of creating an issuance template, you can select to add this template to an API Key.

...

When clicking on “Add to API Key“ a list of the available API keys for your templates will open.

  1. Select the API Key you want to associate with the new template created.

  2. Insert the password provided when creating the API Key.

  3. Callback: Insert the URL of a service that is notified by a post notification with the session data when the session has been validated.

Info

If this is your first template, the creation of an API Key will appear instead. Jump to the tutorial on creating an API Key.

Example

2. Create an API Key

On the API Keys section, click on “New API Key” and set the basic configuration:

  • API Key Name

  • Select the DID associated with the new API Key

  • Select the credential issuance template you want to associate with this API Key from the SSI Operations dropdown.

Make sure to store the API key password in a secure place. Once you close this tab, you will not be able to retrieve the password, you will only be able to access the API Key ID in the API keys list.

3. Connect Wallet to Sandbox

The sandbox will allow you to perform private and secure tests of the platform.

You can access your Sandbox from the dashboard. Scan the QR provided with your wallet, and you’ll be in.

...

4. Test it

...

5. Integrate SSI with your application