You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
The token is generated under "BOT" accounts and I've verified YETIBOT_ADAPTERS_MYMATTERMOST_TOKEN in env output in pod has the correct value.
I don't see anywhere to define what the username - for which this token is valid is defined? Or does this adapter not work with bot accounts ?
The text was updated successfully, but these errors were encountered:
You're welcome to test on it if you'd like. I can set up a bot account for you. Config doesn't require a username - just a token.
My bot under Main menu -> Integrations -> Bot accounts looks like this:
My local adapter config looks like:
:yetibot-adapters-ybmattermost-type"mattermost":yetibot-adapters-ybmattermost-host"yetibot-mattermost.herokuapp.com":yetibot-adapters-ybmattermost-token"asdfaasdfasdfasdfasdfasdfa":yetibot-adapters-ybmattermost-secure"true";; true by default
Login to mattermost returns 401 with this:
A clear and concise description of what the bug is.
The token is generated under "BOT" accounts and I've verified YETIBOT_ADAPTERS_MYMATTERMOST_TOKEN in env output in pod has the correct value.
I don't see anywhere to define what the username - for which this token is valid is defined? Or does this adapter not work with bot accounts ?
The text was updated successfully, but these errors were encountered: