So here is where I’m at. I created a test Slack environment with the free version with a username of “@Paul Fry” and a channel called “#test-channel”. The FOG web gui seems to not be able to pull this info with the legacy token that slack generates. I tried the combinations of the token with my username by itself and the channel name by itself to no avail. I made sure to include the necessary character before each item. Both generate the following error:
This may be a red herring, but the slack api documentation is saying not to use the
channels.list method that is used in the current plugin: https://api.slack.com/methods/channels.list
They say to use the newfangled conversations API that uses the method
conversations.list instead. I am no coder so I can’t seem to figure out how to test this, but here is that API page: https://api.slack.com/methods/conversations.list
This doesn’t explain how it can’t pull a username from the site however. The
users.list method is still supported. I believe the FOG plugin uses this, but somehow still can’t find my username.
As an addendum to all of this, slack seems to be REALLY REALLY wanting to move away from what they call the “legacy token” (what we are using for the plugin) and instead wanting to use their apps platform. I do not know the viability of using this platform, but it looks pretty simple. The info can be found here: https://api.slack.com/custom-integrations/legacy-tokens
I may have time to poke around for a bit this weekend still, but my lack of coding fluency is really showing as I try to decipher what the heck slack wants us to do now.
Pinging @Sebastian-Roth just in case he is curious. You can find the OAuth token (legacy token) on this page when you are logged in (about half way down the page after all the dreck about how you shouldn’t be using it lol) : https://api.slack.com/custom-integrations/legacy-tokens