- 2 minutes to read

ProtectedContextValues - System Parameter

Nodinite encrypts your Context Properties from BizTalk Server and all Nodinite Log Events that stem from other Integration Platforms and custom logging solutions.

To hide a value from a Context property, use the System Parameter ProtectedContextValues.

graph LR subgraph "Nodinite" roNodinite(fal:fa-user-secret Protects) end subgraph "Log Events" ro1(fal:fa-globe HTTP Headers) ro2(BizTalk Context Properties) ro3(MuleSoft Business Events) ro4(Azure Logic Apps Tracked Properties) ro5(...) end roNodinite -.- ro1 roNodinite -.- ro2 roNodinite -.- ro3 roNodinite -.- ro4 roNodinite -.- ro5

Examples of different Context sources

Unlike Microsoft BizTalk Server, where Context Properties are stored in clear text, perfectly readable without any traces for SQL DBAs, Nodinite hides the Context values in the Nodinite Log Databases.

The Web Client provides self-service access to logged data for your Users with Role-based security to Log Views. An administrator may have given Users the right to view Context Data, including passwords for FTPs. When using Dynamic Send Ports in BizTalk; You may want to mask these values for some Context Values.

Example of hiding filenames

[{
	"Key": "http://schemas.microsoft.com/BizTalk/2003/file-properties#ReceivedFileName",
	"DisplayValue": "*** hidden filename ***"
}]

Repeat the entries to hide additional context values,

[{
	"Key": "http://schemas.microsoft.com/BizTalk/2003/file-properties#ReceivedFileName",
	"DisplayValue": "*** hidden filename ***"
},
{
	"Key": "MySchema#Password",
	"DisplayValue": "******** [password is hidden]"
},
{
	"Key": "MySchema#SecureValue",
	"DisplayValue": "•••••••••"
}]

json JSON text string with valid values

This feature comes with Nodinite version 4.3.0.24


Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite System Parameters exist in the Troubleshooting user guide.


Next Step

Administration