WSO2 API Header is not working as expected - wso2-api-manager

I have created API in wso2 API manager and specified header as a required field but when API was hit by using postman I am able to get the response. Do I need to enable header check in any configuration file Please let me know.
I checked WSO2 2.6.0 API documents but did not find solution.

Related

Firebase Auth does not work with Twitter API v2?

Looks like Firebase JS lib doesn't work with Twitter API v2?
I see the following error message.
index.js:1 FirebaseError: Firebase: Failed to fetch resource from
https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true,
http status: 403,
http response: {"errors":[
{"message":"You currently have Essential access which includes access
to Twitter API v2 endpoints only. If you need access to this endpoint,
you’ll need to apply for Elevated access via the Developer Portal.
You can learn more here:
https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve","code":453}]}
If you want to know the steps for Twitter elevated access, please follow the attached image steps:
... for elevated access of Twitter.
You'll need to apply for elevated access on the developer portal.

WSO2 AM - Converting JSON to XML

I want to expose the REST API in WSO2 API Manager with the back-end service (XML over http). I wanted to convert the JSON request to XML and call my back-end service.
Please let me know how to achieve this in WSO2 API Manager 3.0
Use the json-to-xml-in-message mediation sequence.
Login to api publisher.
Open the api and go to the Runtime Configurations tab from the left menu.
In the Request section, click on Edit button of the Message Mediation option.
Select the json-to-xml-in-message mediation sequence from the Common Policies.
Click on Select and Save the api.

Failed to publish API using WSO2 API manager

I am unable to publish API in WSO2 API manager 2.6.0 environments.
Error message is:
Failed to publish Environments
Production and Sandbox
Error while publishing prototype API to the Gateway. Error while publishing API to the Gateway. No API exists by the name
I did checked API in the DB it exist.
I did searched over the net but did not find any solution on this issue.
Looks like Even after deleting the API, still context URI is persist somewhere so I think I need to delete the context URI - Please suggest
I found solution -
Even after deleting the API from WSO2 publisher, Looks like API will not completely deleted from WSO2 so I just checked is there API still exist in WSO2 and I found the API in the below mentioned location and deleted.
API Manager\2.6.0\repository\deployment\server\synapse-configs\default\api
Now I am able to create new API with the context URI.

WSO2: Can IS access token be used for APIM access token for APIs for same users?

When integrating the WSO2 Identity Server (5.6.0) and WSO2 APIM (2.5.0). I came across one scenario where I want the token which I am generating while logging into IS should be used also for invoking APIs in APIM which are created by the same user.
I am creating user in IS and it is getting reflected in APIM but the token which is generated for IS is getting saves in IDN_OAUTH2_ACCESS_TOKEN of IS DB and for APIM while invoking any APIs for the same user, the token are getting saved in IDN_OAUTH2_ACCESS_TOKEN of APIM.
I want to use the same token which was generated in IS to invoke APIs which the same user created in APIM.
Any guidance in this direction will help me to understand.
Thanks
In a distributed deployment of APIM, you can use IS as the key manager node. The following document explains how to set it up.
https://docs.wso2.com/display/AM260/Configuring+WSO2+Identity+Server+as+a+Key+Manager
This document explains (step 3) how to share databases between APIM and IS. You can use the same to achieve what you want.
In short, you need to configure IS to use the APIM DB (shared between 2 nodes) instead of its own IS DB.
You also have to map the Application in the API store to the OAuth app you have created in IS. See this doc for that.
https://docs.wso2.com/display/AM260/Provisioning+Out-of-Band+OAuth+Clients

Manage subscriptions on WSO2 API Manager without API Store Interface

I am using WSO2 API Manager to expose few APIs. But I don't want that the consumer use the API store for the subscriptions. The creation of subscriptions/applications and Access tokens should be managed through by my custom web application.
I have checked the WSO2 API Manager docs https://docs.wso2.com/display/AM210/apidocs/store/ and imported the swagger in SoapUI. When I try to invoke the store api of my local API Manager I am getting the HTML content of API store page. see below screenshot.
Can anyone please help what I am doing wrong? Or is there any other way to the requirement.
You need to pass token which is generated by passing scope and client secret key and password as described in https://docs.wso2.com/display/AM210/apidocs/store/#guide

Resources