« API and Interfaces (Cloud) » : différence entre les versions
Aucun résumé des modifications |
Aucun résumé des modifications |
||
Ligne 5 : | Ligne 5 : | ||
===Export Queues=== | ===Export Queues=== | ||
===Sync Agent=== | ===Sync Agent=== | ||
===Sage FRP reporting API=== | |||
Sage FRP Reporting is a companion Application which is designed over Microsoft Excel. As a data oriented Application it needs to access to the production database. | |||
Because opening the database to external accesses is not an option, a SQL proxy service has been implemented inside the the Sage FRP 1000 Service. | |||
This SQL Proxy service authenticates both the client Application (here Sage FRP Reporting) and the client user : | |||
* The client Application is authenticate using a SAS (Shared access signature) mechanism, similar to the SAS used on Azure services. | |||
* The client user is authenticate as a regular Sage FRP 1000 user. | |||
The SQL proxy implements queries parsing to limit the Client Application access, it also inject the TID filtering terms in case of a multi tenancy database. | |||
===REST API=== | ===REST API=== | ||
[[Category:Cloud]] | [[Category:Cloud]] | ||
[[Category:Architecture]] | [[Category:Architecture]] |
Version du 27 février 2017 à 10:05
Overview
Import Queues
Export Queues
Sync Agent
Sage FRP reporting API
Sage FRP Reporting is a companion Application which is designed over Microsoft Excel. As a data oriented Application it needs to access to the production database.
Because opening the database to external accesses is not an option, a SQL proxy service has been implemented inside the the Sage FRP 1000 Service.
This SQL Proxy service authenticates both the client Application (here Sage FRP Reporting) and the client user :
- The client Application is authenticate using a SAS (Shared access signature) mechanism, similar to the SAS used on Azure services.
- The client user is authenticate as a regular Sage FRP 1000 user.
The SQL proxy implements queries parsing to limit the Client Application access, it also inject the TID filtering terms in case of a multi tenancy database.