Red Hat Bugzilla – Bug 1534467
Can not get expected response while using invalid bearer token
Last modified: 2018-03-28 10:19:33 EDT
openshift v3.9.0-0.19.0 kubernetes v1.9.0-beta1 ASB : 1.1.4 Description of problem: Run curl command in client with an invalid bearer tokern , the response is not readable . In v3.7 , the response is 'Unauthorized' in v3.9 the response is 'no kind is registered for the type v1.Status' How reproducible: always Steps to Reproduce: 1. Get the asb route 2. Run command in client curl -H Authorization: Bearer XXXXXXXXXXXX -sk https://asb-1338-openshift-ansible-service-broker.apps.0115-fre.qe.rhcloud.com/ansible-service-broker/v2/catalog Actual results: Curl response is no kind is registered for the type v1.Status
Updated with PR: https://github.com/openshift/ansible-service-broker/pull/647 With return a v1.Status object from kubernetes now. Example: {"kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "Unauthorized", "reason": "Unauthorized", "code": 401 }
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/RHBA-2018:0489