I am new to WSO2 api manager.I want to configure the existing api in api publisher.
I have few question.
1)After choosing "I have existing Api" radio button, two option populates
a)swagger file b)swagger url.
For first option, from where swagger file will generate? and how to generate?
For second option, which url api publisher expecting?
2)After choosing the swagger url radio button. on next page import option is present which also shows same option as above.Whats use of this option and which one to choose.
I tried with the swagger url in both condition and click on save button then it shows below error message.
{"error" : true, "message" : "Invalid CSRF Token please try refreshing the page."}
Can someone please help me to resolve this issue also please share some link or documentation for configuration of existing api?
In APIM, when you select "I have existing API", that means you already have a swagger document for the API. If that's not what you want (i.e. you don't have a swagger doc), you can proceed with Create New API option.
Edit:
What do you mean by an existing API here? Are you just having a service which needs to be exposed as a manage service? If yes, Create New API is the way to proceed.
Related
Im using a 4.0 version of WSO2. I'm able to get the login page, however im unable to get the option for self-registering in the login page. I have setup as mentioned in docs, however unable to identify what am I missing.
Self register option is available for Developer Portal and not for Publisher and Admin portals. The reasoning behind this is that external users should be able to register under organizations (tenants) and consume the published APIs.
Self signup is enabled my default for super tenant (carbon.super) in Devportal. For other tenants, you might have to enable this manually. Please refer [2] for more information.
[2] - https://apim.docs.wso2.com/en/latest/reference/customize-product/customizations/customizing-the-developer-portal/enabling-or-disabling-self-signup/#disabling-self-signup
I have been using superset. I want to bypass the login page. To do so I did the following in a js file
Got token using login API
Got dashboard URL using dataset find API
I have tried to open the dashboard url and I am getting login page eventhough I already hit login API to get the tokens. I want to know is there any way or build in API in superset to open the superset dashboard bypassing the login page.
Thank you for your support. I have implemented SSO in superset. I have done the following things hope it might be helpful for others.
Inside security folder create your own login/logout method inside init.py file.
Update CUSTOM_SECURITY_MANAGER from None to your custom class(defined inside security folder).
I have followed this link https://github.com/dpgaspar/Flask-AppBuilder/blob/master/flask_appbuilder/security/manager.py.
I'm trying to connect my AWS IoT Button to do an IFTTT Maker Trigger, and it's asking for the API Key. I've looked in the settings of the IFTTT Maker Applet I created, and I don't see anything about an API Key. Any ideas of where else to look inside of IFTTT? They don't have a way to contact IFTTT Tech Support that I could find. Thanks!
In the IFTTT app or through their website whilst logged in, go to My Applets > Services > Webhooks > Settings. The settings page will list your Maker URL, and the key is the alphanumeric string at the end. If you click on the URL, it will take you to your Maker webpage that specifically tells you what your key is, and provides instructions on how to use the webhook.
At the time of this writing, this appears to be the correct place to find the API key:
https://help.ifttt.com/hc/en-us/articles/115010230347-Webhooks-service-FAQ
Under the Documentation Link of the Webhooks service page.
I have some previous experience with the youtube and youtube analytics api where there was an option to use https://developers.google.com/oauthplayground/ to essentially create an offline situation for your own user account api access. By creating the key in the developer console you could add that to a custom oAuth credentials. The user account you were logged into would then generate the access token and refresh token needed. I do not see Google Photos API listed as an option here. I would prefer not to create a website just to get a prompt once (myself).
Any help would be greatly appreciated.
If you are specifically after a token to make your own requests to the API, you can still use the OAuth 2.0 playground. You can enter your own scope in the tool under step 1, just below the list of scopes on the left side. (The text box is labelled "Input your own scopes".)
Here you can manually enter a scope that's listed on the "Authentication and authorization scopes" page in the Google Photos Library API developer documentation.
In step 2, you can access a refresh and access tokens and construct your own request in step 3. Note that you won't be able to List possible operations for this API.
Note that you can also specify your own OAuth client ID and client secret from your own Google developers project. You can find this under the "settings" icon on the right, under "Use your own OAuth credentials". Otherwise, tokens are automatically revoked by the playground after a certain amount of time.
However - If you just want to explore the API through the playground, you can use the version that's embedded in the reference documentation. You can find it on each page for a method, for example mediaItems.list. This version includes support for all API methods and makes it easy to construct correct API requests.
I am using API gate way and I have different methods with different resources. Now that I am done with them I need to export the configuration then in the future I do not have to do it manually again. However the problem is in action I only see the import option. I know for the fact that I can use swagger or API extension to first design the rest calls and then import it to API gate way. But in my case which I have created all the methods manually is there any way I can export them as a json then I can import it again in the future?
First, deploy your API to a stage.
In the API Gateway console, go to the stages page (select "Stages" under your API name in the tree view on the left.)
Click on a stage in the tree view to get to the "Stage Editor" page.
Select the "Export" tab.
On the left is an icon labeled "Export as Swagger". Hover over it and two buttons will appear: "JSON" and "YAML". Click the button for your preferred format. You should get a file save dialog to download the resulting export file.
API Gateway currently does not support exporting your API into a
swagger document.
You may want to create a feature request with AWS to export the
API as a swagger doc.
But, you can create Documentation based on your current API and
publish it from API Gateway console.
Update
Based on comments from #MikeD, API Gateway does support exporting.
Please follow the below document from AWS:
Export an API from API Gateway