It is possible to create REST Endpoints for Deliver instances in TimeXtender. This is a really nice feature that makes it possible to share data in- and externally using API calls instead of directly to a database.
The current implementation is backed by an IIS instance that uses a machine identity to authenticate to the database backing your Prepare instance. The main drawback of this is that there is one static login/user connecting to your datawarehouse, there are no options for more finegrained security than applying a token or oauth to the endpoint.
In my experience many customers would consider using REST to deliver data to third parties. The third parties could be customers or partners that consume parts of a larger dataset. Naturally, this leads to needing to apply table/field or row-level security to filter down the data that can be accessed by a specific token/login.
It would be a great addition if a single Deliver instance can be secured such that Power BI, Qlik, Tableau, REST endpoints can enjoy the same security possiblities. Apart from passing through Windows AD / Entra ID / user:pass (SQL Auth), the REST endpoint would need to be able to map database users to tokens / app registrations.
The current workaround would be to create a separate Deliver instance for each data / security combination that must be delivered. This will quickly lead to an unmanageable amount of Deliver instances, or for customers to look for other solutions.
