Now that Google Apps Vault supports licensing for a subset of users, I'd like to be able to manage Vault users with the Licensing API. However, it seems that while the Reseller API supports Vault as a product and sku, the License Manager API does not.
Thinking maybe the documentation was just lagging as sometimes happens, I tried a licensing.licenseAssignments.listForProduct() API call with Google-Vault as both the productId and skuId as is used in the Reseller API. It returned a 400 error with the message Invalid productId: Google-Vault
Is there a non-reseller way to manage Vault licenses programatically? If not can this be added as an enhancement request?
Try to use VAULT as the productID and Google-Vault as skuID. See if that works!
Related
I am using wso2 apim 4.0.0. Some dozen of apis are deployed and published on it by admin user. Consequently the provider of those apis is admin(in wso2 db). The question that I would like to ask is if it possible to change api provider to another user. If it is then how to do that?
I tried to change it directly in wso2am_db (wso2 api manager database), but haven't succeeded.
this is not possible. Provider is user who created api. You can log in like admin, delete your api. Log in(in publisher or restfull api) like a different user and then create/deploy your api.
The API Provider will always be the user who creates the API. Directly updating the tables may result in data inconsistency. If you want to show it as owned by a different user in Developer Portal, you can add that user as Business Owner of the API, under Business Info.
I'm a newer in wso2 and having some confusions regarding subscribers who log into the developer portal for subscribe to APIs. In fact,i created a user with the role internal\subscriber and internal\selfsignup and after logging in with this user, I expected that he could only see the APIs created and subscribed to them with the applications created in the /publisher page, but it seems that this user has the possibility to create these own applications and I do not see how to withdraw these privileges. I want it to use also the apps created in /publisher.
Best regards
The question is a little confusing. Please find the basic ideas of API visibility and API subscription availability below.
You can create applications in the devportal or store portal
You can create APIs in the publisher portal
In general, when you create an API in the publisher portal and publish it without any role visibility restrictions, anyone can view those APIs. To view these publicly available APIs in devportal, you don't even have to log in to the devportal. This is can be viewed in anonymous mode.
In case if you have restricted the API visibility in devportal based on roles, then only the users with the allowed roles can view those APIs.
Similar to API visibility, you also can control the API subscription in the devportal. The subscription availability option will only be displayed if there are tenants in your environment.
Please refer to the official document for more details on this topic.
Is there any API for Google Cloud - that allows you to create billing payment method to be created?
I can create a billing account for Google Cloud using an API https://cloud.google.com/billing/reference/rest/v1/billingAccounts, however I can't seem to find a way to add payment method to this billing account.
Did any one ran in this problem before?
Google Cloud Billing API is designed to help you manage billing accounts, and their linkage to projects. Google Cloud does not provide an API to add payment information, such as credit card numbers.
Google Cloud's Billing API is designed to comply with PCI Data Security Standards (DSS). According to PCI DSS,
The PCI DSS applies to all entities that store, process, and/or transmit cardholder data.
That means you. If you write an application that stores cardholder data and transmits it programmatically, then you, yourself, may require a PCI DSS assessment of your CDE (cardholder data environment). This is likely not what you intend.
The Stripe API for Payment Methods offers similar guidance:
When creating with a card number, you must meet the requirements for PCI compliance. We strongly recommend using Stripe.js instead of interacting with this API directly.
I am designing a product which would be deployed to AWS. It will use Cognito for user authentication. It will be a multi-tenant application.
The application has many modules/features. The pricing depends on the features selected by the client.
Please provide guidance on how can I implement a check if the feature is licensed or not. I don't want to put the logic inside each web api endpoint.
You should create an application microservice (callable via a API, but with access locked down to your own application) that receives information such as:
Authenticated User ID
Service wanting to be accessed
Resource-level information in case you want fine-grained access control
The authentication microservice would consult a database, apply appropriate business logic and return a success indicator.
Preferably:
Each request should be logged in an audit trail
If access is denied, return an error message that could hint at the reason why (eg 'This feature is requires subscription to the XYZ module')
Use some form of cache to make the queries super-fast (eg DAX for DynamoDB, or ElastiCache)
Licensing systems can often be more complex than actual applications!
I'd like to play with the specific Amazon API that would allow me to look at my own customer data -- e.g. order history. Can anyone tell me which of the numerous APIs I should research?
Check the Web Service API Reference page for more information.