prompt for jetty ssl username and password in stdout when starting SOAP monitor

[selkind]

I'm trying to launch the SOAP monitor for a project using a Tunnel (since the remote server is SSL only), and every time I click on OK I immediately get prompted for a jetty ssl username and password.  It's not coming from the remote server, it's coming from some sort of built-in jetty server since even when I put a bogus IP in the endpoint I get the same prompt.  Any idea what username & password I should be using, or how do I set it?

Extract below from stdin/stdout (I just hit return for username and password).  I'm also attaching a screen shot of the monitor config.  I also added in the remote server's self-signed cert in the trust store I'm using as a trusted cert.


jetty.ssl.password :
jetty.ssl.keypassword :
2009-07-10 15:14:13.311::INFO:  jetty-6.1.x
2009-07-10 15:14:13.311::WARN:  failed SslSocketConnector@0.0.0.0:8081
java.io.FileNotFoundException: C:\Program Files\eviware\soapUI-2.5.1\bin (Access
is denied)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.(FileInputStream.java:106)
        at org.mortbay.resource.FileResource.getInputStream(FileResource.java:27
3)
        at org.mortbay.jetty.security.SslSocketConnector.createFactory(SslSocket
Connector.java:213)
        at org.mortbay.jetty.security.SslSocketConnector.newServerSocket(SslSock
etConnector.java:423)
        at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
        at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:28
3)
        at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:14
7)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
        at org.mortbay.jetty.Server.doStart(Server.java:233)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
        at com.eviware.soapui.impl.wsdl.monitor.SoapMonitorEngineImpl.start(Soap
MonitorEngineImpl.java:95)
        at com.eviware.soapui.impl.wsdl.monitor.SoapMonitor.start(SoapMonitor.ja
va:459)
        at com.eviware.soapui.impl.wsdl.monitor.SoapMonitor.(SoapMonitor.j
ava:153)
        at com.eviware.soapui.impl.wsdl.panels.monitor.SoapMonitorDesktopPanel.<
init>(SoapMonitorDesktopPanel.java:41)
        at com.eviware.soapui.impl.wsdl.actions.monitor.SoapMonitorAction.openSo
apMonitor(SoapMonitorAction.java:170)
        at com.eviware.soapui.impl.wsdl.actions.monitor.SoapMonitorAction.perfor
m(SoapMonitorAction.java:135)
        at com.eviware.soapui.impl.wsdl.actions.monitor.SoapMonitorAction.perfor
m(SoapMonitorAction.java:35)
        at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPer
formed(SwingActionDelegate.java:100)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18
49)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
a:2169)
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
.java:420)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258
)
        at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
        at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1
051)
        at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMen
uItemUI.java:1092)

[selkind]

I think I answered this one myself.  The internal jetty server needs an identity cert for itself with alias "jetty" in an ID store configured in the SOAP monitor setup.  Apparently it requires the https: protocol in the request to the jetty SSL port on the local machine.