This repository consists of a Slackbot that allows Twingate users to self-serve access to different groups according to policies defined by their network administrators. In essence, it brings the concept of profiles to Twingate.
Typical use cases:
- Manage access to resources that share the same IP addresses or DNS names
- Segregate access to different environments (e.g. Development, Test, Production environments)
- Switch between resources in different geographic regions
- Request/approve access to groups
- Time-bound access to groups (resources)
Profiles can be configured in JSON and access to each profile can be restricted based on group membership.
- Slack Workspace (with admin access to deploy)
- A Twingate account
- Ability to deploy a Slackbot (instructions below)
- Create New Slack app from a manifest here
- Paste the content from manifest.yaml
- Install the Slack app to your Workspace
- Retrieve the signing secret from the
Basic Information
page and bot token fromOAuth & Permissions
page
Please prepare the following configuration parameters (refer to the example file):
SLACK_SIGNING_SECRET
Slack signing secretSLACK_BOT_TOKEN
Slack bot token (begins withxoxb-
)TG_API_KEY
can be generated in the Setting page within the Twingate Admin Console (Read and Write permission is required)TG_ACCOUNT
replace with your Twingate Network Address (e.g. test1.twingate.com)PROFILE_CONFIG
Your profile configuration (see notes and guidance in the schema documentation)
- Ensure you have the following pre-requisites:
- All configuration parameters from the
Configuration
section above PROJECT_ID
GCP Project (will be passed to container for it to access secrets)- Google Cloud project owner
- All configuration parameters from the
- Click and follow the steps in GCP CloudShell, entering the configuration parameters when prompted:
The Run on Google Cloud option
will prompt for all pre-requisite parameters during setup and store them as secrets. For a full description of the executed steps please see app.json
.
For a manual deployment you may instead follow the manual instructions
- Go to your app at Slack App UI
- Event Subscription
- Replace the Request URL to
https://{Your tg-group-profile-manager URL}/slack/events
- Replace the Request URL to
- Interactivity & Shortcuts
- Replace the Request URL to
https://{Your tg-group-profile-manager URL}/slack/events
- Replace the Request URL to
- Download the Twingate Logo and change the logo of the Slack app in the
Basic Info
page.
- When there are Twingate groups with duplicate names, only the first group returned by the Twingate API is used. To prevent this, ensure there are no duplicate group names in the Twingate network.
- Only support native Twingate groups and does not support groups synced from IdP
- The Slack users' email addresses needs to be the same as their Twingate email address.
- Group changes will be passed to any connected clients automatically without the need to disconnect and reconnect but please advise end-users that this process can take ~20 seconds to pass through to connected clients.