In wso2 API monetization why subscriber will fill details regarding plan - wso2

In wso2 API manager why subscriber will fill details reagarding plan. As mentioned in the documntation, the user will login and fill the plan for consumption but why he'll decide the billing plan for the consumption.

Looks like a mistake in the docs. As per the screenshot, it's the admin user who's logging in at step 7, but not the newly created user.

Related

How to change api provider in wso2 api manager?

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.

WSO2, not allowed subscribers to create application

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.

How to create a budget with enabling notification channel by using Cloud Billing Budget API

Able to create budgets by leveraging Cloud Billing Budget API but couldn't able to add / enable notification channels for the budget to get an alert .
Please advise .
The default functionality is to send alerts on budget threshold to users with the Billing Account Administrator or Billing Account User role. The console UI allows you to also map Monitoring notification channels, that enables the functionality of customizing the email addresses where threshold alerts get sent. I am not aware of any way to do this through the API.
You can create ThresholdRules through the API, that then send automatic emails to Billing Account Admins and Users (as per the default behaviour). This does not help you if you need a custom email or some other channel to send the notification.
The other thing you can do is configure your own pub/sub topic to receive all updates related to budgets. You can then map a function to programmatically to the pub/sub topic to do something on updates. This is documented at https://cloud.google.com/billing/docs/how-to/budgets-programmatic-notifications
You can also take a look at https://cloud.google.com/billing/docs/reference/budget/rpc/google.cloud.billing.budgets.v1beta1#google.cloud.billing.budgets.v1beta1.AllUpdatesRule.

Metrics for Cognito are not showing up in Cloudwatch

Our team is implementing a Web Application (ReactJS) that utilizes Amazon Cognito service for user sign-up, log-in, log-out.
However, instead of using Cognito's hosted UIs, we created our own login page and used amazon-cognito-identity-js sdk to implement the authentication functionality.
Now, I need to be able to monitor the user activity (for example, which users logged-in from which location). I understand that this can be done by using Cognito's Advanced Security feature.
I have set the user pool's Advanced Security Setting to "Audit Only". However, there are still no Cognito-related metrics showing up in Cloudwatch.
I also tried to follow the instructions described in below site but to no results.
https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-viewing-advanced-security-app.html
Does anyone have any idea as to what setting I may have missed out?
Any advice is highly appreciated.
Cognito will automatically setup Cloudwatch for your User Pool activity. You just need to go to Cloudwatch > Select "Cognito" from the Services list.
Try to refine the time filter or set the refresh interval to make Cloudwatch regularly fetch the newest metrics.
Hope this answers.

wso2 API visibility for subscriber

using wso2 AM 1.10 I published an API logged in as the default admin user. I tried to create a new user using the management console and assigned the Subsriber role to that user. However when i log in to the store using that user, the published API is not visible. I made sure that the API is set to public while publishing the API. Also, I dont see the options in the manage tab as described here. https://docs.wso2.com/display/AM1100/Key+Concepts#KeyConcepts-APIvisibilityandsubscription
What could be the reason for the newly created subsriber not able to view the pubslished API? What is the criteria for the API to show up in store for the newly created subscriber?
For APIs to be visible, the API needs to be in published state and the user's role needs to have subscriber permissions.