I have both my wso2 api manager and wso2 identity server running on the same instance .So I wanted my wso2 identity server to run at port 9444. I restarted my wso2 identity server after adding an offset of 1 in the carbon.xml.
I am getting a 502 Bad gateway error when I try to access my carbon console on 9444 port or any other port.
Are there other places where I need to change the port in the wso2 identity server. I have not changed the port settings in any other config files in the identity server .They are still showing the default port settings
You have to change only port offset in carbon.xml for WSO2 Identity Server. Have a look [1]
[1] https://docs.wso2.com/display/IS570/Default+Ports+of+WSO2+Products
Related
I have configured WSO2 Identity Server following this doc.
But when i log in to my webapp I get the following error :
Connection Refused.
I'm behind a corporate proxy. How should I configure IS server to make it work?
If you are having issues with connecting outside from your network without a proxy, you can use the following jvm parameters during the server startup to provide the proxy configurations.
ex:
sh wso2server.sh -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8000
-Dhttp.nonProxyHosts="localhost|127.0.0.1|10.*.*.*"
In our project, Client has their own KDC server and client want our WSO2 should talk to client KDC for authentication. I know that how to enable kerberos in WSO2 but I am not able to established connection between our WSO2 to client KDC server(In short, i want to connect WSO2 identity server to external KDC server).
We do not support this in the currently released versions of the WSO2 Identity Server. However, we have successfully done an implementation of authentication with an external KDC for Identity Server 5.3.0 release.
You might be able to test this with the next milestone release of Identity Server.
I have proxy service on WSO2 Enterprise Service Bus 4.8.1. It makes pass through proxy to Echo service on the same server. After restart ESB server this service disappears because of
ERROR - ProxyService Error reading from wsdl URI java.net.ConnectException: Connection refused: connect
WARN - Axis2SynapseController The proxy service echoProxy cannot be deployed - Continue in Proxy Service fail-safe mode.
I think that internal service Echo is not started when this service starting and it causes this error. When ESB server is completely started Echo servise is running and it is possible to deploy echoProxy service. But I don't know how.
For your proxy, i believe you used option. That is why you get that error. If you go to repository/deployment/server/synapse/default/proxy folder, you will see the proxy configuration which you created. You can make a copy from that, and after server starts fine, you can deploy that file in the same location. It will be deployed successfully
I want to monitor my ESB using Jconsole and JMX. I can connect to JMX server from the localhost but for connecting from remote machine to my esb I can establish the connection.
I use WSO2 ESB 4.6 and this my JMX configuration in carbon.xml file.
<JMX>
<!--The port RMI registry is exposed-->
<RMIRegistryPort>9999</RMIRegistryPort>
<!--The port RMI server should be exposed-->
<RMIServerPort>11111</RMIServerPort>
</JMX>
I found the problem, my rmi service was running on the host ip which was "127.0.0.1". To connect remotely to the jvm I had to bind the external ip to the hostname. To do this in unix systems use command hostname to get the name of the hostname. Then check the ip that is assigned to the hostname, to find out this use ping $(hostname) you will see that system is pinging the hosname's ip.
If your host ip was the default 127.0.0.1 and you wanted to change it, just edit the file /etc/hosts as superuser. After rebooting the rmi service, you can reach it from the remote machine.
Have a look at wso2carbon.log, you will find an entry like INFO {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL : service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi {org.wso2.carbon.core.init.JMXServerManager}
Use given URL to connect to the carbon server from a remote JMX client (JVisualVM for example) and don't forget to define security credentials (default Username / Password is admin / admin)
I have followed the procedure for cluster deployment of wso2 API manager mentioned in
Referencing: http://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager
But when i am running API manager with different profile wso2 API manager is started but is not accessible from the browser.However, if I change the port offset in carbon.xml to 0 and then r everything runs fine.Please tell me where is the issue.
When you change the port offset in carbon.xml, all default port values will be adjusted according to the port offset values.
If port offset is 2, the default HTTPS port 9443 will be changed 9445 in the run time. So you should access the management console via 9445 port.
Also see following wiki page about changing port offset for API Manager.
http://docs.wso2.org/display/AM160/Changing+the+Default+Ports+with+Offset
I hope this helps