...
Warning | ||
---|---|---|
| ||
The remote console is currently enabled by default, but there is no real the default security mechanism in place is very low. The username and password that are prompted are by default not validated, so any combination will work. In production environment, we recommend disabling the server (by using the client mode) or deploying a JAAS realm to perform some real authentication. See the security documentation. To secure the channel, it is possible to use SSL encryption by changing the url as shown in the #Configuration section. |
Launch options
The ServiceMix Kernel shell scripts supports a number of options to control the remote console:
...
Code Block |
---|
[KERNEL]/etc/org.apache.servicemix.shell.cfg
|
The defaut configuration is as below:
Code Block |
---|
startLocalConsole=${servicemix.startLocalConsole}
startRemoteShell=${servicemix.startRemoteShell}
remoteShellLocation=tcp://0.0.0.0:8101/
|
The port used can easily be changed by changing the default port 8101
in the remoteShellLocation
property.
To switch to a secured channel using SSL encryption, edit the above file and change the remoteShellLocation
property to use SSL as below:
Code Block |
---|
remoteShellLocation=tcp://0.0.0.0:8101/
|
The realm used by the console when authenticating remote users is named RshServer
, so you should override this realm as explained in the 4.5. Security framework. If you want to use your own keystore and truststore when enabling SSL, you can add the following properties to the configuration file:
Code Block |
---|
clientKeyAlias=servicemix
clientKeystore=RshKeystore
clientTruststore=RshTruststore
serverKeyAlias=servicemix
serverKeystore=RshKeystore
serverTruststore=RshTruststore
|
You can either deploy another set of keystores that use the above names or change the named used and deploy new keystores. The key aliases must be set to a valid key in the store that will be used to secure the communication.
Wiki Markup |
---|
{scrollbar} |