Red Hat Bugzilla – Bug 1144894
[RFE] Use https in application URL's
Last modified: 2015-04-06 13:05:57 EDT
Description of problem: Customer policy requires that all URL's use https, including application URL's. Customer requests that the console and other utilities use https when presenting application URL's Version-Release number of selected component (if applicable): 2.1.* How reproducible: Very Steps to Reproduce: N/A Actual results: Current application URL is presented as http://myapp-mydomain.example.com/ Expected results: Present application URL as https://myapp-mydomain.example.com/ Additional info: PR to follow. Implemented as configurable option based on broker.conf boolean:- "APP_REQUIRE_HTTPS" This may be a different solution to BZ 1042920
The existing option in broker.conf can do this? # Whether cartridges that specify direct SSL connection to the gear # are allowed, denied or forced. SSL_ENDPOINT="allow" # SSL_ENDPOINT="deny" # SSL_ENDPOINT="force"
(In reply to Meng Bo from comment #2) > # Whether cartridges that specify direct SSL connection to the gear > # are allowed, denied or forced. > SSL_ENDPOINT="allow" This setting is not really related... has to do with ssl_to_gear in the cartridge manifest, i.e. whether the cartridge can/must handle direct SSL connections at its external port. This bug has to do with what the broker and rhc tell the user is the app's web URL. The app is exposed at both :80 and :443, cleartext and secure, it's just that the cleartext URL is given and they'd like the option to report the secure one instead (especially so if they want to disable the cleartext port).
Created PR #5853
Created updated PR #6101 https://github.com/openshift/origin-server/pull/6101 ... and related PR #2988 https://github.com/openshift/li/pull/2988
Check on puddle[2.2.5/2015-03-18.2] 1. create some apps, and show the apps all url of apps use "http" 2. configure the broker # vim /etc/openshift/broker.conf APP_ADVERTISE_HTTPS="true" 3. create some apps, and show app all url use https
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0779.html