/** * The main template file * * This is the most generic template file in a WordPress theme * and one of the two required files for a theme (the other being style.css). * It is used to display a page when nothing more specific matches a query. * E.g., it puts together the home page when no home.php file exists. * * @link https://developer.wordpress.org/themes/basics/template-hierarchy/ * * @package WordPress * @subpackage Tally * @since 1.0.0 */ ?>
This article explains the unique technology behind the “Tally on Browser” feature in that ensures a complete end-to-end security and privacy of your data.
It is important to understand how a HTTPS communication happens to understand the technology of Tally that allows the Tally on Browser feature.
When we look at HTTPS communication, which is typically between a browser and a ‘web server’, goes through different stages
Brower and web server agree on the TLS versions, cipher suits supported and so on, including the web server sending its SSL certificate to the browser.
The browser validates the certificate for its authenticity that it is talking to the right web server as intended. With this browser, knows that I am talking to whom I am supposed to!
A session is established using a pre-master key and later agreeing on the session keys to encrypt the communications. With this, a secure symmetric encryption is achieved between the browser and the web server
With the established session and security, application layer communication starts. i.e. asking for certain data to server and server responding with the data and so on.
(Steps to get a secure Browser Access of your data)
The Tally.ERP9 running on the desktop acts as a ‘HTTPS client’ and connect to the ‘Browser Proxy Service’ on the cloud. It is done using the above HTTPS based communication. The Tally establishes a dual channel communication (one for client’s requesting things to server, and other for the Server to respond back to client on events)
Here, Browser acting as a HTTPS client, talks to our systems to do authentication of Tally.NET Identity and post that, listing the companies that are accessible to the logged in user.
Browser acts as a HTTPS client. The browser establishes connection with the Browser Proxy Service.
This is where the interesting things happen. The browser does the initial handshake, authentication (as in the HTTPS stages above), with the ‘Browser Proxy Service’. Here, the browser being HTTPS client, and our Browser Proxy Service on cloud acting as a HTTPS web server.
With successful handshake and authentication and after validating the ‘user / company’ being accessed, the browser proxy service, short-circuit the connection with the browser and Tally.ERP9 (right instance which had the company data and the browser), itself acting as ‘Proxy’ as the name suggests.
With this, the further steps of session establishment and application layer communication happens between the browser and Tally.ERP9. Yes, here while browser continuous to acts as the ‘HTTPS client’, the Tally.ERP9 on the desktop, acts as the HTTS web server.
Making session establishment and providing REST protocol-based application communication to access various reports.
GST Changes – Joint Development Agreement Developer’s Point of View