We're CSP partner trying to implement change notifications for user resource.
Is there a chance to create a one subscription (on partner level) and be able to get notifications for our customers?
Other words, if we have 50 000 customers, does this mean that the only way to retrieve notifications for all of them is to create subscription for each of them (50 000 subscriptions in this case) ?
Regards ,
Pavle Kukric
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 working on a web application which is based on Google App Engine (GAE). The requirement of the application is that one user can be associated with multiple company accounts.
My application has two main types of accounts. One is that main Admin/Company account. Other is the employee account (i.e. the persons who work under a company). Now, what I want to do is that to allow an employee to work under more than one companies, but he does not have to make a separate account for each company. His single account can be associated with multiple companies.
I have explored different platforms which are already supporting this feature. The major ones which I found are Slack and Asana. And my problem can be perfectly mapped to what Slack is doing right now i.e. I create a single account on Slack and I can join multiple workspaces on Slack using this single account.
I want to achieve the same in my application too. I am curious that how Slack is supporting this feature right now? Does it send some ID with every request to the server which indicates that the activity which just has been done is associated with the workspace under this ID? Or there is some unique sort of token associated with every workspace (on Slack API level)?
I do have such a model in my app. A unique auth_token is associated with every company account. So, I am thinking that when an employee wants to do an activity for a specific company he will send this unique token with the request to the server so that server knows for which company the activity was performed.
Does anybody know what is the best way of achieving this?
There are two different concepts at work here:
Relation between account and company / workspace
The data structure for the Slack account is designed such that it can be linked to multiple Slack workspaces, e.g. in SQL you would have a many-2-many relation between the accounts and the workspaces table.
Staying logged in
The way Slack and others Single-Sign-On provides like Google SSO keep you logged in is by settings a browser cookie. That cookie would usually be some kind of crypto hash and the SSO provider will use it to identify to which account the current user belongs to or to request a login via OAuth if the cookie is missing / invalid.
This can also be achieved partly with server sessions (which also uses cookies). Using server sessions is easier to implement than implementing your own (secure) cookie solution, however the user will only stay logged in as long as the browser stays open. But that should be sufficient for most solutions.
Note that tokens for the Slack API work very differently. e.g. they have to be generated per workspace, user and app.
I have dropbox webhooks. When a user make a change, this webhook sends me a json with the list of users that have changes.
If some user in my platform, that has the drobox active, doesn't pay the quota so it's "inactive", there's a way to stop receiving his webhooks?
The only solution that I've thought is to store the inactive users and ignore when his id is equals to the id on the json, but that's quite ineficient because if I have 1000 users inactive that's a huge amount of webhooks to ignore.
No, it's not possible to exclude users that are over quota from webhook notifications. We'll consider it a feature request.
Currently, payments processed through certain credit card processors (example: Authorize.net) can be set to first authorize the fund, then later capture them when prompted in the UI via the admin interface.
I am hoping to capture funds of authorized orders (Big Commerce status 'awaiting payment') via the API rather than through the UI. I have not been able to find anything but a post from 3 years ago saying it was not yet possible. Is there now a way, or is this still something that cannot be done?
old thread: Is it possible to "capture funds" for authorized credit card transactions via the API?
It isn't possible to capture funds via the API today. The API is meant to Create, Read, Update, or Destroy entries and nothing is exposed to the API that would allow you to execute an action between BigCommerce's core application and the payment gateway .
I am using android gcm to make push notifications for my users. Everything is working so fine. To send a notification I need the users registration id to identify him. It works. Now my problem is that I have some hundreds of users and I would like to inform them ALL about certain updates.
Is there a way to send a notification to all users?
Do I really have to push them all by their registration ids?
On the server side I am using PHP and CURL as it is shown in many examples around here...
There is no way to broadcast to all users with a single post.
You need to send every ID in blocks of up to 1000 ID's. So if you have 2500 ID's, you need to split that up into 3 posts. 1-1000, 1001-2000, 2001-2500.
If you want to use the new GCM topics you could create a "all users" topic, and have the app subscribe to that topic when it starts up. Then a single topic post could go to all the users (I think the limit is a million but you probably should check that).