Slack down right now12/31/2023 ![]() On our company’s workspace, we have something like 350. On our testing workspace, we have maybe ten channels. Once we decided to dogfood the app and try it out on our own workspace, it broke completely. It’s kind of a pain in the butt, but it worked fine on our testing environments. We give workspace admins an opt-in setting that instructs the bot to automatically join all public channels, which has to be done one by one. The bot just has to join all of the channels that one might want to send notifications to. Without the incoming webhook URLs, we were restricted to scopes available to our Slack bot.įor public channels, this wasn’t much of a problem. But we still had to figure out how to get notifications sent to the right channels. With these updated scopes and without the incoming webhooks, we made some InfoSec teams quite happy and they were green-lighting our applications. They had actually asked us to disable this feature because it opened a new angle of attack. For some of our more security conscious customers, this was a big no-no. Now we (and anyone who got a hold of our logs) could spoof whatever messages they want to corporate Slack channels. If one of these URLs returned an error, that has potential to get logged on our side. We decided to stop using incoming webhooks for a good reason: improved security. These URLs were automatically generated, so that Stack Overflow for Teams had easy access to post to any channel. These are URLs that we could post to whenever we wanted to send a notification to a channel. Previously, the mechanism were used for notifications was incoming webhooks. ![]() You can configure Stack Overflow for Teams to send a notification for a channel whenever there’s activity you are interested in. One of the primary features of the Slack integration is notifications. Authentication and permissions for the granular bot In this article, we’ll talk about how we built this new version and the path we took to ensure our new bot useful, usable, and secure. Asking you all to upgrade only to lose functionality would have been a hard sell. We had to do a fair bit of work to make sure that the new granular bot version had feature parity with what we had previously. We wouldn’t have been able to implement the features in this release without them. While we had been planning to include features that built on workspace apps, Slack was such an incredible partner on this that we were able to pivot smoothly.They reached out and gave us a shared support channel and were incredibly responsive to our support questions. When the developer preview for the feature ended, they recognized that this was the wrong path for them, and they deprecated workspace apps. We had originally worked with Slack to be one of their launch partners in implementing their workspace apps. So the work we’ve done here sets us up to provide even more functionality in future versions. A one-click autoupdater that uses a modal dialog to make sure the app is current on all associated workspaces.Īdditionally, our previous integrations were built on functionality that has since been deprecated.Ask questions directly from Slack with /stack ask.Org-wide installs, so organizations with multiple Slack workspaces can add our integration to all of them at once.A more secure and configurable authorization experience.This version brings several new features that will improve your overall experience: For reference, the integration that most people use was version two version one was a bare-bones integration that just supported notifications (and is still used by a small fraction of Teams). There’s a lot of great new features, and a lot of work behind the scenes to make them a reality. With this release (available for Basic and Business today, for Enterprise in the 2021.1 release), we wanted to dig into some of the technical details of what we did. We’re pleased to announce that we’re releasing version three of our Slack integration with plenty of new features to reduce context and tool switching while streamlining the developer workflow. It’s now one of the most popular ways for users to interact with our platform, and we have been steadily upgrading it with new functionality based on feedback from customers. In 2018, we released an integration between Stack Overflow for Teams and Slack.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |