botium-core icon indicating copy to clipboard operation
botium-core copied to clipboard

Published 20 hours ago • verified publisher icon codeforequity-at

Cannot connect Botium to an SOE which acts as Watson Assistant proxy

Open andrewrfreed opened this issue 2 years ago • 2 comments

Describe the bug The WA botium connector is not working with a classic SOE A customer uses an SOE that proxies their Watson Assistant v1 instance and it expects to be called with Basic authentication. (Authorization: Basic base_64_encoded_apikey_colon_actualapikey) The SOE application wants to manage the IAM token relationship on its own, not have Botium manage it. This seems like it should be possible in Botium if a different authenticator is used. The SOE itself is difficult to update.

I've been unable to test but will submit what code I expect could work.

To Reproduce Configure WA botium connect without using the apikey. .env file should have BOTIUM_WATSON_USER and BOTIUM_WATSON_PASSWORD.

Expected behavior Botium should connect to the SOE which proxies Watson Assistant, configured only with BOTIUM_WATSON_USER=apikey and BOTIUM_WATSON_PASSWORD=the_actual_api_key

Screenshots and Log files botium-wa-connector

Botium Flavour:

  • Botium Core

Botium Version

  • Latest

Additional context Possible solution (untested): https://github.com/codeforequity-at/botium-connector-watson/pull/28

andrewrfreed avatar Jul 07 '22 21:07 andrewrfreed

Right, this is a thing that wasn't considered in the Botium connector yet.

codeforequity-at avatar Jul 11 '22 13:07 codeforequity-at