Revision # |
|
1.25 |
Authors |
|
Thomas Jespersen (CTO) |
Intro
Templafy is a cloud based Content Enablement Platform. It integrates into Microsoft Office 2016/2019, Microsoft Office 365, and Google Workspace. It can be configured and customized to meet the needs of any organization in the world – no matter the size.
Templafy has a rich set of features to help Users easily generate new documents that are up to date with regard to Visual Identity, Corporate data, User data, Legal information and shared content.
Diagram of PaaS and Customer Infrastructure
Technical prerequisites
Technology
|
Front-end: TypeScript, React, WPF Backend: .NET 5, VSTO Hosting: Azure, Docker, Kubernetes (AKS), Web Apps, Azure SQL, etc. |
Browser support |
Microsoft Edge Google Chrome Mozilla Firefox Apple Safari |
Cloud platform,
|
Web site and backend is hosted on Microsoft Azure Kubernetes and stores data in Azure Platform as a Service (PaaS). Microsoft Azure is certified with ISO 27001 and PCI DSS among other. For more information on Microsoft Azure security and compliance: Microsoft Azure provides SLA of 99,95% for Kubernetes (website and API) and 99,99% for data storage. For info on Microsoft SLA: |
Scaling |
Templafy uses Microsoft Azure Kubernetes automatic scaling of web sites. New instances are automatically spun up based on activity on web server. Database and Azure backend features are configured for performance. |
Geofencing |
Templafy is hosted in multiple Azure Data Center regions like: EU, US, and AU and guarantees that tenant data does not leave the region |
Data storage |
Data are stored in SQL Azure. Files are stored in Azure Blob storage. Both types of storage are considered highly secure and reliable (eg. all data is saved on 3 disks and has geo redundancy to other data center within geographical region). |
Guest and
|
The Microsoft Azure backend ensures that no other Microsoft Azure customer can access our data. Isolated data containers for each customer/client with no direct access and a web based access control system ensures that a user can only see data for the customer for which the User is signed on. Role based system ensures that a User can only perform tasks in the system to which the User has been assigned privileges. All controllers in the system have authentication filters to ensure guest isolation. |
Encryption |
All internal communication between server and client is SSL encrypted. All data in transit is SSL (TLS) encrypted. All data at rest are encrypted. |
Open Source components |
A selection of secure and qualified Open Source components are used and are constantly monitored for patches and security vulnerabilities. |
Third party tools |
A few Third party tools are used for sending mails and tracking product usage |
Authentication |
Any SAML2 based Authentication Service (e.g. ADFS, Ping Federate, OKTA, Airwatch, etc.) Open ID Connect like Azure AD OAuth 2.0 based authentication providers like Google |
SCIMSingle Sign-On |
Templafy supports SCIM - read more here Azure AD via App in Azure AD ADFS, Ping Federate, OKTA, and SAML2 Open ID Connect |
Protection |
Object Relational Mapper protects against SQL injections. Client side binding framework protects against XSS attacks. Unique per session token required for all backend calls protects against XSRF attacks. |
Logging |
Operations performed by users and administrators. Successful and failed log-ins are logged. |
File types supported |
docx, pptx, xlsx, pdf, jpg, png, .svg. More file types are added continuously. |
Ports used for communication between device and application |
HTTPS (443) port only |
Comments
0 comments
Article is closed for comments.