I have an API in WSO2 API manger 1.8 and Production URL with a third party rest end point.Here the third party rest have 'Location' header with some valid contents.But during the API call the API manger redirecting with some invalid URL (location key conatins in the response of rest end point and considered as the URL ) and getting error in wso2 console
Issue fixed by changing the plugin .This issue already fixed by WSO2 and fix updated in WSO2 ESB ,but fix not updated in WSO2 AM.
This is the JIRA link ,
https://wso2.org/jira/browse/ESBJAVA-3461
https://wso2.org/jira/browse/APIMANAGER-3818
Related
Im using django restframework python in local its working fine as excepted (get,put,post,delete).Ran the server gave the endpoints in api manager and configured resources also,deployed.Get and delete method is working fine in wso2 apim ,but post and put method doesnt work.when i hit postman with required payload it goes to wso2 apim but in backend am getting null
i debugged at end backend (got to know payload becomes empty).i tried to find logs in wso2 apim
I'm trying to implement OAuth2 Authorization Code flow with WSO2 APIM 2.6 but I get a 405 method not allowed. Here is what I did
Intall WSO2 APIM (no WOS2 IS nor IS-KM is in my environment. only APIM is present)
Create a spring boot REST service with #Restcontroller. This leads to base path as http://localhost:8080
Create an API in API publisher. This point to the REST service
As admin create an application in API store and subscribe to the API. The call back URL is simply http://localhost:8080 as shown in the image below
Call the authorize method of WSO2 APIM with the following URL
https://localhost:9443/authorize?response_type=code&redirect_uri=http://localhost:8080&client_id=EaTfmmwQT4fWciN4WnU1YyyYYYsa
When I call this URL, I'm redirected to the login page of WSO2 APIM like below
I just log in with admin/admin
Upon login, I though I'd be redirected to a authorize page, but instead I'm redirected to the following error page
Coul you guyz help me here ?
You are trying with https://localhost:9443/authorize which is wrong. That is why it is redirecting to the carbon console. You can use one of the following URLs.
https://localhost:9443/oauth2/authorize
https://localhost:8243/authorize
This will prompt you to a different login page where you can use your login credentials.
https://docs.wso2.com/display/AM260/Authorization+Code+Grant
Hi I have imported an existing soap wsdl using wso2 api 2.1.0 manager.
I have the option to download the wsdl, to my local machine.
But what i want is to be able to access the newly created wsdl using an url.
How is this possible ?
Got the url from the
{you host name}/registry/resource/_system/governance/apimgt/applicationdata/wsdls/{your api name}.wsdl
you can also change the file type to text/xml in the metadata of the wsdl , so that it's directly viewable from the browser.
I have wso2 apim 2.1 and I have request to connect to SOAP endpoint which is secured with username and password.
During add procedure of SOAP endpoint I dont have possibility to enter such credentials nor possiblity to use mediation(eg like for rest api) as I get not authorized before enetring next phase. is there a way how to do this without using ESB ?
how to connect to secured SOAP backend using just apim ?
or Do I have to use ESB and follow similar way as LINK
thank you for any advice
We were not able to parse the backend wsdl from some reason and we have done workaround by donwloading wsdl and manualy pushing it to registry, after that we were able to follow next steps.
I'm using wso2am 2.0.0 and trying to configure SSO for access to the store and publisher application.
I'm not using wso2 IS but just configured the api manager directly to my IdP server(I have edited the site.json file to with my IdP setting)
I'm getting this exception after being authenticated to my IdP:
SAML Response contains invalid number of assertions. {org.wso2.carbon.hostobjects.sso.SAMLSSORelyingPartyObject}
It look like my SAML response isn't correct but i'm unable to find why?
There was no problem with my SAML response .
The problem was caused by a difference between my IdP server and the api manager timezone (they are deployed in two different environment), so the exception is thrown when comparing the current time in the gateway with the NotBefore/NotOnOrAfter
So may be a more significant error message could help
You can use an online SAML Response decoders like this and see what's wrong with you SAML response.
Another option is to use SAML Tracer in firefox.