XML encrypt/decrypt

[Norbert_B]

---

@AmitKaria2k wrote:

Hello,

Encryption in XML file is required to encrypt the various configuration parameter values so that a user cannot view / edited it external outside the to the test application. [...]

---

A report is a result of a test. So it will never be read out again by TestStand for reading of parameters. So changing values in a report file will not change anything in the test system.You are correct, that the parameters are part of the report (if selected) and there is no default way to "grant user right based access" to those parameter values. So if the endcustomer is not to view parameter values, you have to either exclude them from the report at all, or to modify the reporting mechanism from TestStand.

Since the reporting mechanism in TestStand for XML is not as easy as for HTML or ASCII, you will have to find your way through it.

In regard to the amount of values you want to encrypt, this can be quite worksome.....

hope this helps,

Norbert

[AmitKaria2k]

@ Norbert: Just to be clear, the encryption will be required in configuration file & not for report so that important device settings are not modified outside my application

[AmitKaria2k]

Hi Ashwin,

I guess even I was doing the same as what your code does. But probably you are right, I may have to touch the XML style sheet to display the information.

I'm a neophyte in TestStand & XML & hence any further help on displaying the added data through XML stylesheet would be highly appreciated !

Thanks

[Norbert_B]

Ok, then meddling with the reporting of TestStand is completly the wrong position to start with.

If you write a TestStand Sequence for performing your tests, you create steps which evaluate the unit under test which need to be parametrized (e.g. Numeric Limit Step needs limits and comparison type). Those parameters are stored within the Sequence File.

The default file format for Sequence Files is binary, so nobody can access those parameters. Even if someone changes bits and bytes in there, the only result will be that the Sequence File gets corrupted.

In addition to those "static" parameters, you can use external files or a database for storage of parameters. Those can be loaded during runtime using the Property Loader Step. Using files (txt, csv or xls) will naturally result in readable and changeable parameters if the user knows where those files are expected (folder).

Therefore, i suggest you to use a database for best protection of those information if they are sensible.

hope this helps,

Norbert

[Ashwin_S]

---

@AmitKaria2k wrote:

@ Norbert: Just to be clear, the encryption will be required in configuration file & not for report so that important device settings are not modified outside my application

---

Norbert is right, Database it is a Good Way of securing the Data. What is still confusing is, why the Report  needs to be Encrypted?.

AshwiN,  

[AmitKaria2k]

You both are right.. but above all the client is... It's is his requirement to use XML instead of database & secure the vital config data by using encryption feature of XML. 🙂

[Ashwin_S]

Hello Amit,

http://forums.ni.com/t5/NI-TestStand/Teststand-Report-Format-Stylesheet-Help/td-p/1509162 , just an Example of how to modify a Style Sheet.

The basics of XSLT @ http://www.w3.org/TR/xslt

You have to add some code in the Horizontal.xsl (if you are using) to parse the corresponding newly added XML node and publish it in the Report. Understanding of how the Horizontal.xls is working will make your work easier.

AshwiN,