Cogmento CRM is a VCM, a verifiable credential management system, and a compelling and hyper-configurable CRM platform. A VCM allows you to manage the issuance and verification of verified credentials at scale. The marriage of CRM and VCM is perfect, as you already hold the subject data and can use it to create elaborate schemas that represent your data and processes and encapsulate them in credentials.
Currently, Cogmento CRM implements verified credentials on top of Microsoft's platform, which means the credentials can be held and presented using the MS Authenticator application and Microsoft Entra Verified ID, which enables Zero Trust security.
This small web application demonstrates how a simple integration with Cogmento can lead to the collection of contact information while issuing the person a verified credential, which they can later present for verification.
First, you must create an account on Cogmento CRM and collect the API token associated with a user. You can find your API token in the User Manager section, which is under Settings:
You will also need to create a Verified Credentials Schema. Schemas define what is actually in your credential. For this demo we'd like a credential that encapsulates a contact and deal records. In the schema form you'll have Contact and Deal both checked. Within those record types, select First Name, Last Name, Email and the Deal's Title. Thoes are the fields we will include in our Verified Credential.
The rest of the Schema configuration is up to you.
You will require the schema id, which is available to the right after the schema is created (within the JSON representation of it):
Optionally, if you'd like to use reCaptcha for the public submission form, collect your reCaptcha account's key and secret.
Copy the file .env.sample from the root of this directory to a new file named .env and set the values within to those collected, i.e., the API token, Schema id and optionally reCaptcha key, and secret.
To run the web app demo, you can use the run.sh shell script or the Docker container setup.
That is, either:
./run.sh
or
docker run --rm -it -p 8000:8000 $(docker build -q .)
The app will generate the contact and deal records for whoever fills in the form presented at http://localhost:8000 (which, of course, in a real deployment, you'll present under https and a valid domain). As a response, the person will be presented with a credential they can scan into MS Authenticator's Identity wallet.