codeforequity-at / codeforequity-at/botium-core

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

Open
#689 2 comments 0 reactions 1 assignee Claimed by @codeforequity-at View on GitHub
enhancement wontfix
Dominant language
JavaScript
Stars
251
Forks
70
Avg merge
3h 37m
Merged PRs (30d)
7

Description

**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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.