Testing WebHooks

When developing server-to-server applications, it is important to be able to test webhooks without leaking sensitive or private information. To avoid having to use 3^rd party services, such as webhook.site a new package has been made available containing a service that can be installed on any Neuron®, that allows you to view incoming POST requests in a similar fashion.

Installable Package

The Web-Hook Tester service has been made into a package that can be downloaded and installed on any TAG Neuron. If your Neuron is connected to the TAG Neuron network, you can install the package using the following information:

Package information
Package	TAG.WebHookTester.package
Installation key	Mb9pim8FTjHBnju2f2ZVNHBRbOG3VHhM7iBn26mgcvc/uwjouWjHEF0OmcC/noKEuZAOWZY6Ka4A4abb4fc2a2596e04f047400e3218dcd2
Repository	WebHookTester repository at GitHub

Installing the package via the administrative console (Chat Admin), can be done using the following command:

install nobackup TAG.WebHookTester.package Mb9pim8FTjHBnju2f2ZVNHBRbOG3VHhM7iBn26mgcvc/uwjouWjHEF0OmcC/noKEuZAOWZY6Ka4A4abb4fc2a2596e04f047400e3218dcd2

Starting service

The WebHook tester service appears in the administrative portal, in the Software section:

Pressing it, opens the following page: https://lab.tagroot.io/WebHookTester/Show.md

Note: This page does not require client authentication, and can be used anonymously.

Note 2: You can also use the script prompt to make custom POST calls to the page. This requires elevated privileges however, and cannot be done anonymously.

Creating a Page

Enter an ID and press the Start button to create a new page you can POST to. Since the service can be accessible by anyone, use an ID that is difficult to guess, if you do not want others to get easy access to the information. Press the Randomize button to create a random ID. You can customize the random ID to remember the purpose of the page, if you have multiple pages open.

Test Page

When you press the Start button, a new page is opened. It contains instructions how you can POST to the page:

Use the URL presented to POST to the page. If you want to test a back-end service integration, this is the URL you provide as a webhook callback URL. Any POST made to this URL will be displayed on the page.

Note: Nothing is saved or persisted on the page. The page does not remember previous POSTs, so if you refresh the page you loose the information on the page.

Note 2: Make sure to differentiate between the URL of the page (which points to a resource with extension .md) and the URL to POST to (which points to a resource with extension .ws).

Incoming POSTs

As soon as an incoming POST is made, it is displayed on the page as follows. It displays the time of the event, any HTTP headers in the request, together with a textual representation of the payload (if content is text-based), as well as the binary payload, BASE64-encoded. Each POST is presented in its own SECTION tag on the page.

Responses

The response to a POST call to the resource will be a JSON object with one property called Forwarded, which indicate the number of pages the information was forwarded to. If this number is 0, the page has closed or lost contact with the Neuron. Example:

{
	"Forwarded":1
}

Tunneling POST request over XMPP

As the Neuron is connected to the XMPP network as well, since it is hosted on the IoT Gateway, the POST request can be tunneled over the XMPP network using the httpx:// URI scheme. This permits you to do callbacks to local development machines, or machines not accessible via the Internet.

To achieve this, you need to perform the call from another instance hosted on the IoT Gateway. It can be the IoT Gateway itself, Lil’Sis’ or another instance of the TAG Neuron, including a development version on a local machine. You replace the https scheme in the URI with the httpx URI scheme, and replace the host with the JID of the recipient. For the call to succeed, the sender and receiver need to be friends, i.e. have approved presence subscriptions, for the call over XMPP to be possible.

This can be easily tested using the script prompt:

Note: Any software using the Waher.Content Internet Content-Type abstraction, and the InternetContent content access methods, together with the Waher.Networking.XMPP.HTTPX library (containing the httpx URI scheme definition) will automatically support httpx URIs.

Note 2: Since the QuickLogin API and RemoteLogin API are both hosted on the TAG Neuron®, you can register httpx callback URIs with these APIs. This makes it possible to host the recipient service behind a firewall, as long as it supports the HTTP over XMPP protocol

#new, #features, #package, #repository, #neuron, #service

NodeJs installable package

github: https://github.com/Trust-Anchor-Group/TAG.NodeJs

Free package which installs Node JS version 24.11.1 on the running TAG Neuron® at $AppDataFolder/Packages/nodejs/node\.exe

Installable Package

The Node JS installer has been made into a package that can be downloaded and installed on any TAG Neuron. To create a package, that can be distributed or installed, you begin by creating a manifest file. This repository contains a manifest file called TAG.NodeJs.manifest. It defines the content files included in the package. You then use the Waher.Utility.Install and Waher.Utility.Sign command-line tools in the IoT Gateway repository, to create a package file and cryptographically sign it for secure distribution across the Neuron network.

The Node JS installer is published as a package on TAG Neurons. If your Neuron is connected to this network, you can install the package using the following information:

Package information
Package	TAG.Nodejs.package
Installation key	aKY7N1VcoNeDvWXRTyLSoP1ZmrkPkIrh6nIgffiOrjM9Ix+qkT9C7lWn8O2NCcZ/PmuSO9T6S/uA1535b7c39de3bfd6f8f762ce76c92053
More Information

Usage

The package does not set the machines PATH environment variable to enable use of

node index.js	

in a terminal, you have to specify the full path (eg: C:/Program Data/IoT Gateway/Packages/nodejs/node.exe) or use the runtime setting using web script (.ws)

exec := GetSetting("NodeJS.Executable.Path", "");  
ShellExecute(exec, "index.js", "");

or in c#

string ExecPath = await RuntimeSettings.GetAsync("NodeJS.Executable.Path", string.Empty);

Settings Page

The settings page is /NodeJs/Settings.md.

#package, #neuron, #javascript, #node

Neuro Exchange Theme

The Neuro Exchange theme has been made into a package that can be downloaded and installed on any TAG Neuron. You can configure to use this theme in the Theme menu accessible from the admin dashboard.

Package information
Package	TAG.NeuroExchange.Theme
Installation key	BGVWw9FYGj6+mY8nxScZgoKRC8SiV80mWJhHXfUZL3ASrwZSab5PdEwmyfwpJVUEWEMNST4HWayA1640d45c2eae16ecf48e883c75dd25f7
More Information	https://github.com/Trust-Anchor-Group/TAG.NeuroExchange.Theme

#package, #theme, #neuron, #repository

TAG.Stripe package update

Mayor changes:

• Able to pay with the browser (no smart contracts).
• Uses webhooks instead of polling for confirming payment.
• Supports TST as currency if the connected Stripe account is in test mode.

IMPORTANT:

There is currently no way to confirm if the contract version of the flow actually works since TAG do not have access to create PaymentMethod‘s with the Stipe api.

How to use webflow

Setup

1. In the neuron’s Stripe settings panel you have to specify everythin and set the Payment flow to “Prefer web redirection”. This will make sure the service chooses not to use contracts.

Buying edaler with the agent api

1. Login as a user with a valid wallet and id.
2. use /Wallet/InitiateBuyEDaler to initiate payment.
3. You will get an event form the neuron’s event pipeline (websocket) where if everything when correctly you will get a url for the payment. You can:

a) Choose to redirect (or open a new page) the user and make the payment on the default payment page.

b) Extreact the clientSecret and create the Stripe Payment Elements yourself.

4. Now after all payment details are submitted, the payment should be complete and edaler appere in the wallet.

Notes:

• If you use the default payment page, you can set successUrl to specify where to send the user after a succesfull payment. If not specified it will go to the default page.

TST as currency

If you development neuron uses TST as a currency, the stripe implementation will treat it as EUR but only and only if the Stripe account is in test mode, otherwise it will reject the request. TLDR: if you use TST as currency, Stripe have to be in test mode.

#neuron, #stripe, #edaler, #package, #update

Agent API Javascript NPM package

Currently, there is no package on the public npm package registry, but you can still add the package as a dependency in your package.json. You just add

“agent-api”: “https/github.com/Trust-Anchor-Group/AgentApiJavascript.gitnpm-package”

to your dependencies. Though, note that this might require that you have the newest version of the AgentApi on your neuron (which may require the newest neuron version). This is because the repo is designed for the latest version, which means that it might be different since the AgentApi is ever evolving. And at last, there currently is only one version, which if it is updated, and you later install your dependencies, the package might have changed. So if you for some reason do not plan to update the neuron or your code, it might be better to copy the code in the package. For those curious, there is currently not a package for the typescript version.

In The Code

if you use ES6 import syntax just use : `js import AgentAPI from "agent-api" AgentApi.Legal.CreateContract()

or if you use CommonJs: `js const AgentAPI = require("agent-api") AgentApi.Legal.CreateContract()

The Github Repository

As you may see, the package is located in the npm-package branch on the AgentApiJavascript repository on Github. If you notice that the main branch have got some important commits that the npm-package does not, please consider rebasing the npm-package branch to the main branch. If you are not sure how to rebase, consider learning more about it, absolutely use something like Sourcetree to check that you did it right, and if you are worried, make a backup of the repo.

#javascript, #npm, #package, #agentapi