Relative Content

Tag Archive for wso2wso2-api-manager

Wso2 4.4.0 Can not APIM manager Advanced UI Customization

I am having problem doing Advanced UI Customization I have followed the steps to edit the look and feel of the devportal. I copied the wso2 webapps file to another folder and ran npm install, then npm run bootstrap, then went to the devportal folder and ran npm run build dev. But I tried to overwrite a React file in the folder where I copied webapps. Then I rebuilt and copied the dist file and there was an overwritten file of React. But I copied the dist file in the webapps folder (coppy) to the webapps folder (root) and also the index.jsp file, but then I ran the api-manager.bat –run command again and didn’t see any change in the interface. . Please help me know where I went wrong. I am using wso2 4.4.0. I have read the document and followed it but I don’t see any change. Can you help me please. I followed these steps: https://apim.docs.wso2.com/en/latest/reference/customize-product/customizations/advanced-ui-customization/

EC certificate for hostname instead of RSA

I have changed the hostname of WSO2, i imported the new certificate to wso2carbon.jks and configured, when trying to login in publisher for example i cant login and i have this error:

Gateway [SCR] Error while trying to bind reference

I’m following the steps given in WSO2 GIT Repo here. Did the all the configs as instructed. Placed the jar in lib folder and confirmed its reflected in dropins too when the server starts. Am I missing anything here?

WSO2 API Manager (wso2am-2.1.0) – Empty Response from API When the Accept Header is Passed

I’m using wso2am-2.1.0 and I’ve created an API calling to a particular backend endpoint. The endpoint and the API responds fine. However, when I pass the Accept:application/json header, as per requirement, the API gives an empty response with a 200 OK status code.
The backend when invoked directly without the accept header responds with an xml with the xml content type header and when invoked with the Accept:application/json header, it responds with application/octet-stream header.
A direction to resolve this issue is much appreciated. Thanks in advance.