We have implemented row level security in our SSAS database. In our business case we have property level security and account level security. In property level security user should be able to see data for only those properties which are assigned to him, and in Account Level security a user should be able to see data of only those accounts for which he is authorized to access.
After security implementation we noticed a problem due account level security implementation, users were not able to see correct totals for those hierarchies which were having some accounts which were not accessible to the user due to security restriction. e.g. if a user is head of purchase department he is having access to sales accounts only, but when he browse cube for net profit he is seeing wrong net profit, as the net profit only calculates based on sales department accounts.
I want to know for the possible solution to sort out this issue.
Related
I have an app users can create groups with each other, and want to sell (via monthly subscription) premium groups with some extra features.
With in-app-purchase, admin of group can convert it to premium group. And i store that info at database like groupstate: premium or groupstate: free. Depending on that child group becomes premium or stills free.
So when admin cancels the subscription, with check on every app start I can get the subscription info, cancel the subscription and turn group state to free. But if admin never logs in; I cant check the subscription is valid or not and other users will be able to use premium.
What kind of structure do i need to avoid that ? Any suggestions ?
I am just trying out the open-API specs provided by tmforum https://www.tmforum.org/open-apis/ and cannot seem to figure out the difference and actual purpose of the financial account resource mentioned in account management API specs. Can someone please elaborate?
The financial account aggregates the amounts of one or more billing accounts owned by a given party. For example, as a customer, I may have multiple billing accounts (e.g. for broadband services for multiple properties) - the financial account is the aggregation of these billing accounts.
I'm working on a startup and we plan to use Plaid API or Yodlee for banking data aggregation ie credit history and previous transactions. I wanted to know about the data policy of these services from a fellow programmer who has worked on it. The sales guys give a pretty garbled view.
My questions are mainly
If one of my users had previously given their data to these
aggregators (ie maybe used Yodlee for mint) do they have to put in
each of their bank login details again if they use my service or do
they have a sort of user profile with which they can authorize my
app to view the data stored in their service.
Does Plaid API/Yodlee use the data I generate for its own uses and
do my users owe these data to these services and not me?
If I want to move out do they still hold my users data (the bank
accounts they have signed up with)as a profile on their desk?
PS: I think this question follows SO's policy but feel free to correct me if not.
Is there a way to get transactions for all container accounts that belong to a specific site aggregated using Yodle APIs?
For example, the American Express Cards (siteId: 12) have bank, credits, loans and etc enabled containers.
So, can we get the transactions for all enabled container accounts for a single site?
If you mean to ask this- "Is there a way to get transactions for all the accounts(all containers) belongs to a particular site?" Then.
Yodlee provides two ways to get the transactions.
Getting transactions for a specific account i.e., you need to provide itemAccountId for each account to get the transactions for the specific account using executeUserSearchRequest API.
Getting transactions for all the accounts i.e., you need not to provide itemAccountId for any of the particular account while provide rest of the input parameters to get transactions using executeUserSearchRequest but this will return you transactions for all the accounts. Using your example, it will give you transactions for all the container present under SiteID-12 as well as other sites added by the consumer. Though you can use the second approach to get the transactions for all accounts and then filter it out for all containers belongs to a specific site. You can use the sumInfoId(ContentServiceID) present in the response for each transaction.
Does anyone know of any solution for checking that a user is still employed by the company who pays for their access to my web app? The problem I'm trying to address is that my client's admin users aren't great at killing the accounts of users who no longer work for that company.
It would be ideal if there were some generic way of asking a company's HR system "Does employee 0001 still work for you?"
Currently working with a very small user base, so acquiring more info on users (e.g. employee reference number etc.) is relatively easy.
Thanks.
No, there is no way to reliably check for this. However, that's not the problem, your approach is. Give the company an incentive to validate the accounts. Either charge a fixed fee on top of any usage charges so that dormant accounts cost them money, or make the accounts go dormant after a short period of time such as a month so that the client is forced to revalidate periodically.