Revision # |
|
1.25 |
Authors |
|
Thomas Jespersen (CTO) |
Intro
Templafy is a cloud based template management system. It integrates into Microsoft Office 2010-2016, Office 365 Pro Plus with 2013 and 2016 Apps, SharePoint Online for Office 365 and Google Drive. 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
Technology
|
Microsoft ASP .NET 4.5, MVC 5, WebApi, Windows Forms and VSTO Responsive HTML5 React.js and TypeScript SPA. |
Browser support |
Microsoft Internet Explorer 10+ and Edge Google Chrome Mozilla Firefox Apple Safari for Mac |
Cloud platform,
|
Web site and backend is hosted on Microsoft Azure Platform as a Service (PaaS). Microsoft is in charge of uptime and patching of servers. 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 web servers (website and API) and 99,9% for data storage. For info on Microsoft SLA: |
Scaling |
Templafy uses Microsoft Azure 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. |
Patching |
Microsoft is responsible for server patching. |
Backup |
Daily backup of Website, SQL Database and Blob storage. |
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 few Open Source components are used for JSON serialization, Unit Tests, Code minification and other non-critical parts of the system. |
Third party tools |
Third party tools like Google Analytics, SendGrid, etc. are used but none of these services have access to internal systems. They are either JavaScript on our web pages or APIs called by code. |
Authentication |
Any SAML2 or WS-Federation based Authentication Service (e.g. ADFS, Ping Federate, OKTA, Airwatch, WAYF, etc.) OAuth 2.0 based authentication providers like Google and Microsoft Office 365. |
SCIMSingle Sign-On |
Templafy supports SCIM - read more here Azure AD via App in Azure AD ADFS, Ping Federate, OKTA, etc.: WS-Federation 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.