This post has NOT been accepted by the mailing list yet.
Quick trick could be with apache http server proxy. Configure apache with HTTPS and forward all your request for admin interface (give some pattern in URL www.xyz.com/openesbAdmin) to localhost:4848 and serve your request.
-------- Original Message --------
Subject: OpenESB SE Admin interface via HTTPS
Date: Tue, April 25, 2017 4:10 am
To: "param.singh" <[hidden email]>
what's the trick to move OpenESB SE's admin interface (port 4848) from HTTP to HTTPS?
If you reply to this email, your message will be added to the discussion below:
well, yes, a reverse proxy is certainly a possible approach. But as we're talking about the ESB's *administration* interface, I'd hope for something more immediate, if possible. Apart from that, the standalone's USP is its small footprint. Too bad, if I have to put a proxy in front just do screen port 4848. But still thanks for the suggestion. :-)
Have you checked in your latest changes? I have 'git pulled' and built the source but still geht the 'instance not available' error. The variable substitution works, though. So, thanks already for this part of the fix. :-)
Well, I've pulled the latest changes, built a new revision and tested again. I made sure I flushed the browser cache but I still get the 'instance not available' error. This is true for oeadmin.sh, too, by the way. Seems as if there is something still missing...
Woah! Just saw, that your changes do not belong to the openesb-standalone git project but are part of openesb-web-console. Apparently openesb-standalone frontend is developed in a separate project and then only copied to the openesb-standalone project as a sort of library. I wasn't aware of that.