Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-12189

Custom API connector integration securityDefinitions issue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.7-GA
    • fuse-7.x-GA, fuse-7.5-GA
    • Fuse Online
    • % %
    • fuse-7.7-build6
    • Workaround Exists
    • Hide

      The security definition that is not used can be deleted from the OpenAPI document which then results in the correct behavior.

      Show
      The security definition that is not used can be deleted from the OpenAPI document which then results in the correct behavior.
    • Hide

      1. Create custom API connector using attached OpenAPI document (select authentication by header)
      2. Create simple integration Timer -> custom API connector (sent requests can be checked with requestbin.com)
      3. See the parameter with placeholder added to the url of the service

      Show
      1. Create custom API connector using attached OpenAPI document (select authentication by header) 2. Create simple integration Timer -> custom API connector (sent requests can be checked with requestbin.com) 3. See the parameter with placeholder added to the url of the service

      When I try to create custom API connector using this document api.json and accept the Header type as the one that should be used, The integration that uses such connector still send both header and query parameter (header contains the right API key, query parameter contains just a placeholde -

      {api_key}

      ).

      This can be reproduced when creating just a simple timer -> custom API connector integration.

        1. api.json
          1 kB

            pcongius Pasquale Congiusti
            jsafarik@redhat.com Jan Safarik
            Jan Safarik Jan Safarik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: