From 864521787ff15d3cd2bf70a9c8df25b6b1dd88e6 Mon Sep 17 00:00:00 2001 From: sofia Date: Thu, 29 Aug 2024 10:49:22 +0000 Subject: [PATCH] Update docs/asset-implementation.md --- docs/asset-implementation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/asset-implementation.md b/docs/asset-implementation.md index f165e51..f8dc7b4 100644 --- a/docs/asset-implementation.md +++ b/docs/asset-implementation.md @@ -15,7 +15,7 @@ The basis of the M2M mechanism are the following: an user account, etc. Each request performed by `asset-api` to `identity-api` is signed using the pubkey pair, which allows the `identity-api` to verify -that the requester is the `asset-api` using the retrieved public key. (Implementation: [$/identity-api/src/m2m.js](../identity-api/src/m2m.js)) +that the requester is the `asset-api` using the retrieved public key. (Implementation: [$/identity-api/src/m2m.ts](../identity-api/src/m2m.ts)) The request body is signed in a PGP-like manner, this can be seen by accessing the index page of the `asset-api` ([http://localhost:3001/](http://localhost:3001/) in default local environments).