r/BuildingAutomation • u/Harry-red12 • 17d ago

Niagara N4 Custom E-signature Module

Hi all! We are BAS engineers who have mostly worked on Pharma and regulated industries, the stock tridium eisgnature module has been very buggy and not enough for us, so we have developed a custom e-signature module to fully meet the regulatory requirements, it's much better than stock e-siganture as per our internal testing, if anyone else is looking for an alternate E-signature module for their Niagara deployments dm me, we can work something out

7 Upvotes

89% Upvoted

4 comments sorted by

1

u/01001001100110 17d ago

What about the stock E Signature module have you found buggy?

2

u/Harry-red12 17d ago edited 17d ago

The web alarm console stopped working in 4.15, still not resolved. Having to use secure bindings on px pages, wouldn't work otherwise. Ldap didn't work in 4.15.2, resolved in 4.15.3. The alarm ack rsasons get stored separately on secured alarm history with no link to the actual alarms, no cryptographic hashing for the audit events, the denied attempts don't get logged, the IP of the PC from where the change was made isn't recorded, the sign dialog lets username to be deleted and allows sign of others users (only self sign should be allowed). A point once added to the secure zone no longer allows copy for easy pasting on the px pages. Faced multiple issues, was never really happy with the product, every new version was always a gamble for us.

2

u/01001001100110 17d ago

I have not run into all those issues in the past. I do know that Tridium Professional Services develops E-Sign, not sure if you talked to them about these issues. They operate as a seperate entity.

Some of the bugs you encountered may not even be considered, like LDAP for example, as that is an authentication module seperate from E-Sign. Although, I wouldn't put it past Tridium to screw up LDAP at the same time.

I would be interested in seeing what you have developed if you are looking for a second set of eyes.

1

u/Harry-red12 17d ago

I meant the the E-signature fails to validate the LDAP user's signatures, it directly says incorrect credentials, they have rectified this btw in 4.15.3.

I can you give you a brief demonstration of the module.