My application is working in a docker container in port 80. I'm planning to integrate SSO with this application, we are using OAM apache webgate to integrate SSO. I need help in structuring this integration.
I previously integrated apache webgate with my docker container directly and got into a state like, i cannot rebuild my image anymore.
Can i integrate apache webgate on my host and still integrate SSO with application inside docker?
Yes you can. OAM WebGate is just like any other apache plugin/module and can work inside the docker container.
Related
Hi i've an application of that i hosted in docker, that is an openfire (xmpp) server , the openfire has several feature like web client and located in port localhost:7443/inverse for example
in my server that contain docker I've managed several application to use reverse proxy and working fine, but I cannot do on localhost:7443/inverse to https://webapp.localhost
Please give me some advice how to do it on apache2 webserver
I have created a VM behind an external load balancer in Azure and I am using IIS as the reverse proxy webserver to host the asp.net core application.
I am able to access the application inside the VM using localhost but not able to access the same from my client machine through the public ip configured for the loadbalancer.
I have configured loadbalancing rules for incoming traffic on port 80 and port 443 for the loadbalancer and specified appropriate NSGs for those ports.
Before deploying the asp.net core application I was able to access the defaultwebsite from my client machine. so I assume that inbound rules are taken in to account and working fine.
This is a self contained application and since I am able to access the application inside the VM through localhost I assume that the aspnet hosting module and other configuration required is proper.
Please let me know if there is anything else I can be missing.
I guess i have figured out what the issue is.
The Loadbalancer probe for the application is configured to be Http since its a webserver and is instructed to check at the default path "/" and since the application i have created does not serve anything on "/" its considering the node as unhealthy and does not respond or serve anything.
I changed the probe to tcp and it works just fine.
Thanks,
Teja
Our current environment has Tomcat containers sitting behind an Apache Web Server. Basically the web server has ProxyPass rules that we use to decide which Tomcat instance to route to based on the context root.
As part of our local gradle build, we are using the Cargo plugin to spin up a local tomcat container and deploying our war's to it. I haven't found anything that will let us spin up an Apache WebServer to test our apache config.
Our goal is to have two Tomcat containers, A and B, and one Apache WebServer C, such that C will route localhost/appA to tomcat A and localhost/appB to tomcat B.
This is all in an effort to run automated acceptance tests, but I have not found a gradle plugin like cargo that will do this.
Thanks!
You can use Gradle to deploy either an Apache http docker or a haproxy docker http://gitlove.us/p/million12/docker-haproxy to do the load balancing to your two appA and appB tomcat containers. You could also use docker for the tomcat containers. You could also use Amazon AWS for two Amazon Linux tomcat servers and either an elastic load balancer or a separate haproxy server for load balancing.
I have a windows 8.1 machine running ubuntu 14.x on a virtualbox. I'm running meteor inside that virtualbox. I've bridged the connection and turned off the firewall on both machines. I'm able to connect to the internet from the virtual box, and I can telnet from the windows host into the ubuntu machine.
I can also connect to meteor apps that are not using the force-ssl package; however, I CANNOT connect to meteor apps that are using force-ssl!
If I run "meteor remove force-ssl" I can connect to the app. Any thoughts? Thanks.
EDIT - by connect to the app, I mean "http://[ip_address_of_guest]:3000/" in a browser on the host machine. I've tried both http and https.
I'm new to Meteor but, from this documentation, it looks to me like you are seeing the intended behaviour ...
"This package, part of Webapp, causes Meteor to redirect insecure
connections (HTTP) to a secure URL (HTTPS). Use this package to ensure
that communication to the server is always encrypted to protect users
from active spoofing attacks.
To simplify development, unencrypted connections from localhost are
always accepted over HTTP.
Application bundles (meteor bundle) do not include an HTTPS server or
certificate. A proxy server that terminates SSL in front of a Meteor
bundle must set the standard x-forwarded-proto header for the
force-ssl package to work.
Applications deployed to meteor.com subdomains with meteor deploy are
automatically served via HTTPS using Meteor's certificate."
This answer clarifies.
I am about to try the Digital Ocean guide, "How To Deploy a Meteor.js Application on Ubuntu 14.04 with Nginx", myself to see if it correctly documents the required set up steps. I'll update with my results.
We have a Glassfish running behind an Apache Webserver. Direct requests to the application server are blocked by the firewall. So we have the webserver forwarding requests to the app server via mod_jk. This all works fine for the web apps deployed on x80 ports of Glassfish. But am now left wondering, how do I access the Admin Console GUI? I can do most of the Admin Console things using asadmin, but it'd be good to have the GUI as well.
Thanks!
Nirav
Why not create a new VirtualHost or an Alias which will map to the Glassfish admin console?