Security
An application built with TX Text Control .NET Server is secured in three places: at the endpoints that the Document Editor and the Document Viewer add to it, in the documents it creates and on the servers it runs on. TX Text Control runs entirely in your environment and leaves the decision about who may do what to your application. For developers who take such an application to production, and for the teams who review it, the pages of Security explain what TX Text Control provides in each place and what the application adds.
Where Security Applies
- The endpoints. The Document Editor connects over a WebSocket at
/api/TXWebSocket, the Document Viewer calls a controller namedTextControl, and your own controllers load, save and sign documents. ASP.NET Core authentication, access tokens and a check of the WebSocket handshake decide who may use them. - The documents. PDF documents can be encrypted and restricted with permissions, documents can be protected while they're edited, confidential text can be redacted and hidden data removed, and digital signatures make changes detectable.
- The deployment. HTTPS, a Document Editor backend that only your application reaches, accounts with few rights and secrets that stay out of the output protect the servers. Signed SBOMs of the TX Text Control packages and the compliance topics complete the picture.
Find the Right Page
| If you want to | Read |
|---|---|
| Understand where documents are processed and which endpoints and ports an application exposes | Security Overview |
| Require signed-in users, apply policies and check access to each document | Authentication |
| Protect the editor and the viewer with tokens, for example for Angular or React frontends | Access Tokens |
| Check the WebSocket handshake of the Document Editor and restrict its origins | WebSocket Security |
| Encrypt PDF documents, protect documents in the editor, redact text and remove hidden data | Document Security |
| Keep signing certificates safe and accept signed documents only from your own signing processes | Digital Signatures |
| Get the SBOMs of the TX Text Control packages and check your dependencies for vulnerabilities | SBOM |
| Harden a production deployment: HTTPS, the backend port, accounts, secrets and updates | Secure Deployment |
| Answer questions about archiving, accessibility, signatures, data protection and the Cyber Resilience Act | Compliance |
Where to Start
- Security Overview: the parts of an application and what each of them needs.
- Authentication: protect the endpoints of the editor, the viewer and your controllers.
- WebSocket Security when your application uses the Document Editor, and Access Tokens when its frontend runs on another origin.
- Secure Deployment before the application goes into production.
The Deployment Guide shows the complete setup of each platform, and Digital Signatures covers signing documents from the first certificate to validation.