Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-1782

Ves Collector has wrong configuration of header.authlist in blueprint

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Medium Medium
    • El Alto Release
    • Dublin Release, El Alto Release
    • None
    • None

      Currently released version of Ves Collector blueprint (1.4.5) has bad configuration of header.authlist.

      Currently when I check it in Consul it is:

      "header.authlist": "sample1,c2FtcGxlMQo="}

      But Ves Collector expects:

      "header.authlist": "sample1,$2a$10$0buh.2WeYwN868YMwnNNEuNEAMNYVU9.FSMJGyIKV3dGET/7oGOi6"}

       

      Effect is that when auth.method is set to BasicAuth, then authentication by sample1:sample1 is not possible and VES returnes answer {"requestError":{"PolicyException":

      {"messageId":"POL2000","text":"Unauthorized user"}

      }

            vv770d vv770d
            mprzybys mprzybys
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: