Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1498992 - Ansible Service Broker template should default ENABLE_BASIC_AUTH to false
Ansible Service Broker template should default ENABLE_BASIC_AUTH to false
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
unspecified
All All
unspecified Severity low
: ---
: 3.7.0
Assigned To: David Zager
Weihua Meng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-05 14:39 EDT by David Zager
Modified: 2017-11-28 17:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:15:02 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Description David Zager 2017-10-05 14:39:22 EDT
Description of problem:

ENABLE_BASIC_AUTH should default to false because the service catalog (by default) is configured to use token based authentication to communicate with the broker.


How reproducible: Always


Steps to Reproduce:
1. Look at the deploy-ansible-service-broker template's ENABLE_BASIC_AUTH parameter.

Actual results: true


Expected results: false
Comment 4 Weihua Meng 2017-10-26 23:11:27 EDT
Fixed.
oc new-app -f https://raw.githubusercontent.com/openshift/ansible-service-broker/master/templates/deploy-ansible-service-broker.template.yaml

$ oc get cm -o yaml -n ansible-service-broker
...
      broker:
        ...
        auth:
          - type: basic
            enabled: false
Comment 7 errata-xmlrpc 2017-11-28 17:15:02 EST
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://access.redhat.com/errata/RHSA-2017:3188

Note You need to log in before you can comment on or make changes to this bug.