Multi-Tenant SaaS?

Kahuna

Looking at Aware IM it seems a perfect environment to build multi-tenant apps but I cant find any documentation on a simple way to do that.

I have seen one post that suggested that adding an attribute to a login (such as a Client Name) and then appending a where on every SQL search as a way to do this, but that seems very error prone and misses the simplicity of other environments where a filter is applied at the outset of a Client log-in.

Is there a simpler way to manage multi-tenancy in Aware IM?

aware_support

This has been answered many times on this forum - please do a search.

I believe some info is also available on the FAQ page of our web site.

kklosson

I have developed a multi-tenant app and have used the concept of the "Account" as a means to filter content to the user. Yes, every query includes something like: ...AND AccountID=LoggedInUser.AccountID.

Never had a problem.

Kahuna

aware_support wrote
This has been answered many times on this forum - please do a search.

I believe some info is also available on the FAQ page of our web site.

I tried SaaS and multi-tenant as a search and little came up - Google raised a couple of threads regarding system members though which discussed the use of READ PROTECT.

So, since you are reading (Aware-Support) can you confirm what the best method of multi-tenant support is? I cant believe that every query will need to be modified, so is the READ PROTECT the option recommended for SaaS support?

Perhaps a discussion in the docs or the FAQ using the industry standard terms of Saas or multi-tenant could support others looking at Aware IM as a development environment?

BTW the more I dig into this tool the more I like it, looks like a couple of additions or even explanations (though I've only scratched the surface on the docs) on things like SaaS and generating UUID's etc would certainly support the move from other environments to Aware IM.

Hope I don't wear out my welcome here - already had some great feedback, but doubtless as I move forward in the next 24 days I will have more questions.

aware_support

Yes, using READ PROTECT is enough. Aware IM will automatically modify all queries for you.

An altogether different approach is to deploy the same application into different business spaces - one business space per client. This should only be done if the number of tenants is not overly large (few dozen, perhaps)

nlarson

aware_support wrote
Yes, using READ PROTECT is enough. Aware IM will automatically modify all queries for you.

Support can you confirm this works for documents? Unless changed recently READ PROTECT does not work for document outputs, so it is best to include the limiter in any queries used with reports.

aware_support

Yes, it probably does not work with documents...

Kahuna

aware_support wrote
Yes, it probably does not work with documents...

Can you clarify what does not work with documents?

Is it that content printed to reports is not limited by the SaaS READ PROTECT, and therefore only the reports data source needs to be limited to the tenant ID over and above that protect? Is it more in-depth?

Or did I miss a point?

aware_support

You are right - this is exactly what I meant. Just protect the data source for reports/documents separately, the rest will be handled by READ PROTECT.

READ PROTECT not working for documents is probably just a bug