Slack ignores CAPTCHA_HANDLER_TOKEN

[AlexP11223]

Looks like Slack always uses token from SLACK_TOKEN ignoring CAPTCHA_HANDLER_TOKEN.

streetmerchant/src/messaging/slack.ts

Lines 6 to 7 in d652b49

	const {channel, token} = config.notifications.slack;
	const {pollInterval, responseTimeout, userId} = config.captchaHandler;

I guess it should either try CAPTCHA_HANDLER_TOKEN first when calling getSlackCaptchaInputAsync, and then maybe fallback to SLACK_TOKEN if empty, or the documentation needs to be updated.

@klords

[klords]

Thanks, will get this fixed right away. We definitely want both tokens to be honored (even if they will practically always be the same).

…

On Sat, Apr 24, 2021, 2:44 AM Alex Pantechovskis ***@***.***> wrote: Looks like Slack always uses token from SLACK_TOKEN ignoring CAPTCHA_HANDLER_TOKEN. https://github.com/jef/streetmerchant/blob/d652b4936435377d36268141a2b63c8798f7f95b/src/messaging/slack.ts#L6-L7 I guess it should either try CAPTCHA_HANDLER_TOKEN first when calling getSlackCaptchaInputAsync, and then maybe fallback to SLACK_TOKEN if empty, or the documentation needs to be updated. @klords <https://github.com/klords> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2428>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACD4CILW7ZPGVWZIIU2WVXTTKKHH5ANCNFSM43P7BBOA> .