INTEGRATION FOR SLACK

App authentication

Our app enables Slack organization owners to securely store their authentication tokens using Hashicorp Vault. Here's a breakdown of the process:

1. OAuth v2 Process:
   Our app follows the standard OAuth v2 procedure as outlined by Slack here.
2. Adding to Slack: On selecting the 'Add to Slack' button, users are directed to the appropriate authorization link (/oauth/v2/authorize).
3. Authorization: Slack will guide the organization owner back to SteelEye's Redirect URL while sending a temporary code (valid for a span of 10 minutes).
4. Token Exchange: SteelEye's listener service utilizes the authorization code from the previous step and communicates with the oauth.v2.access API endpoint (https://api.slack.com/methods/oauth.v2.access) to exchange the code for an access token.
5. Token Storage: The secured access token finds its place in Hashicorp Vault. This is where our ingestion services can retrieve it.
6. Usage: Once stored in Vault, the token grants us the ability to tap into Slack APIs, allowing us to gather messages, edits, deletions, files, and reactions.