🔒Certify
Dernière mise à jour
Dernière mise à jour
How to start using Certify when you're onboarding with the Archipels Back OfficeHere is the URL of the Archipels Back Office : https://certify.archipels.io/It needed to login or signin to the Archipels Back Office to use the Archipels Certify solution. Once you're on the Archipels Back Office, follow the instructions. After having registering yourself as a Trusted Source, you can go to the How to Certify ? page to certify proof.
In a .env file or with environment variables, you must set the following variables in order to make requests to the Trust Registry.
TRUST_REGISTRY_URL: The URL of the Trust Registry API
Production: https://api.archipels.io/trust-registry/v1/
TRUST_REGISTRY_API_KEY: The API key to access the Trust Registry API
Now you can run the SDK API in a container (using a .env file):
The version is provided when given the TRUST_REGISTRY_API_KEY.
Once the container has started, the Open API interactive documentation is accessible on http://localhost:3000/docs.
This operation is done without any communication with Trust Registry API.
The algorithm can be EDDSA or ECDSA.
This operation will return this type of json :
In an .env file or directly in your run environment, you need to add the following variables in order to create or register your identity :
PUBLIC_KEY: public key used to sign data, cf. 1.a.i.2https://www.notion.so/archipels/Documentation-technique-16657e86376d4368874c5be64f57a12d#48558e34443146e6a9a1f9e309cd64ce0
PRIVATE_KEY: private key used to sign data, cf. 1.a.i.2https://www.notion.so/archipels/Documentation-technique-16657e86376d4368874c5be64f57a12d#48558e34443146e6a9a1f9e309d64ce0
ALGORITHM: signature algorithm used EDDSAor ECDSA
WARNING : When deploying the Certify solution in production, you cannot create your own identity, Archipels will provide your ISSUER_ID on demand. So you may skip this step.
There are the instructions for the sandbox deployment.
To create your identity, you need three environment variables : the TRUST_REGISTRY_URL, the TRUST_REGISTRY_API_KEY and the SDK_API_URL: where the API SDK is deployed.
To execute the command you need :
one mandatory argument : the "pub_key" :"<PUBLIC_KEY>"
two optionals arguments : the metadata including the name "name" of your identity (we recommend to associatemetadata) and its description"description"
your issuer_id if you want to choose one especially. If you don’t, it will create an issuer_id for you. You need to save it from the response, since it will be used to identify you.
To register your identity in the Trust Registry use this code:
If you get the error connect ECONNREFUSED, check if you have the TRUST_REGISTRY_URL set.
The returned json will be like:
Now you have all the elements you need to complete your .env file. You must add the issuer_id you just created to your environment so that you have ISSUER_ID = "<issuer_id>"
Here is an example of a complete .env file :
Once completed, you are able to certify schemas and proofs on Archipels thanks to the How to Certify ? page.
Getting started with Archipels' Back Office
Getting started without BO (with Archipels' permission)
Certify a proof