
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
service-msgdistribution-node
Advanced tools
This microservice is distributes messages to one or many recipients using their configured delivery methods: email or sms.
The microservice currently supports the following deployment options:
This microservice has optional dependencies on the following microservices:
Logical contract of the microservice is presented below. For physical implementation (HTTP/REST, Thrift, Seneca, Lambda, etc.), please, refer to documentation of the specific protocol.
class MessageV1 {
public template: string;
public from: string;
public subject: any;
public text: any;
public html: any;
}
interface IMessageDistributionV1 {
sendMessageToRecipient(correlationId: string, recipientId: string, subscription: string,
message: MessageV1, parameters: ConfigParams, method: string): Promise<void>;
sendMessageToRecipients(correlationId: string, recipientIds: string[], subscription: string,
message: MessageV1, parameters: ConfigParams, method: string): Promise<void>;
}
Message can be defined directly or loaded from message template (stored in msgtemplates service);
When message is set directly its subject, text and html content can be set by handlebars template, that it processed using parameters set. Here is an example:
Dear {{ name }},
<p/>
Please, help us to verify your email address. Your verification code is {{ code }}.
<p/>
Click on the
<a href="{{ clientUrl }}/#/verify_email?server_url={{ serverUrl }}&email={{ email }}&code={{ code }}">link</a>
to complete verification procedure
<p/>
---<br/>
{{ signature }}
Right now the only way to get the microservice is to check it out directly from github repository
git clone git@bitbucket.org:entinco/eic-services-users.git
Pip.Service team is working to implement packaging and make stable releases available for your as zip downloadable archieves.
Add config.yml file to the root of the microservice folder and set configuration parameters. As the starting point you can use example configuration from config.example.yml file. Example of microservice configuration
---
- descriptor: "service-commons:logger:console:default:1.0"
level: "trace"
- descriptor: "service-msgdistribution:controller:default:default:1.0"
- descriptor: "service-msgdistribution:service:commandable-http:default:1.0"
connection:
protocol: "http"
host: "0.0.0.0"
port: 8080
For more information on the microservice configuration see Configuration Guide.
Start the microservice using the command:
node run
The easiest way to work with the microservice is to use client SDK. The complete list of available client SDKs for different languages is listed in the Quick Links
If you use Node.js then you should add dependency to the client SDK into package.json file of your project
{
...
"dependencies": {
....
"client-msgdistribution-node": "^1.0.*",
...
}
}
Inside your code get the reference to the client SDK
var sdk = new require('client-msgdistribution-node');
Define client configuration parameters that match configuration of the microservice external API
// Client configuration
var config = {
connection: {
protocol: 'http',
host: 'localhost',
port: 8080
}
};
Instantiate the client and open connection to the microservice
// Create the client instance
var client = sdk.MessageDistributionHttpClientV1(config);
// Connect to the microservice
try {
await client.open(null);
// Work with the microservice
...
} catch(err) {
console.error('Connection to the microservice failed');
console.error(err);
}
Now the client is ready to perform operations
// Send email message to address
await client.sendMessageToRecipient(
null, '123', null,
{
subject: 'Test',
text: 'This is a test message. Please, ignore it'
},
null, 'all',
);
This microservice was created and currently maintained by Sergey Seroukhov.
FAQs
Message distribution microservice in Node.js / ES2017
We found that service-msgdistribution-node demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.