A lightweight module for integrating your Django application with Slack.
- Django >= 1.8
To use Slack OAuth in your Django app, you'll need your SLACK_CLIENT_ID
and SLACK_CLIENT_SECRET
which can be found when you Create a New Slack Application.
Note: This README is currently out of date if it is in my (Micah Lyle's) repository. I changed a few things around to better work with an application I am working on at the moment (09/11/2018).
-
Install using pip:
$ pip install django-slack-oauth
-
Add
django_slack_oauth
toINSTALLED_APPS
insettings.py
:INSTALLED_APPS = ( ... 'django_slack_oauth', )
-
Run initial migrations:
$ python manage.py migrate
-
Add Slack OAuth base url to your project's
urls.py
:urlpatterns = [ ... url(r'^slack/', include('django_slack_oauth.urls')), ... ]
-
Specify your Slack credentials and OAuth Scope in
settings.py
:SLACK_CLIENT_ID = os.environ.get('SLACK_CLIENT_ID') SLACK_CLIENT_SECRET = os.environ.get('SLACK_CLIENT_SECRET') SLACK_SCOPE = 'admin,bot'
If you aren't sure what your scope should be, read more about Slack OAuth Scopes.
Add a link to Slack OAuth in one of your templates:
<a href='{% url 'slack_auth' %}'>Get slacked</a>
After clicking it, you will be redirected to Slack for the OAuth process. If successful, you will be redirected to a view showing a success message. You can change this view by setting SLACK_SUCCESS_REDIRECT_URL
in settings.py
.
You can then view the successful request and API data in the Admin under Slack OAuth Requests.
Pipelines allow you to create actions after a successful OAuth authentication. Some use cases may be:
- Register an account for the user
- Capture returned API data from Slack after authentication (Default Behaviour)
- Send Slack messages to the user's Slack team after authentication
They are simply a list of functions, which get called in order. They must accept and return two parameters: request
and api_data
, containing the initial request and returned API data respectively.
Pipelines are defined as a list of callables in settings.py
:
SLACK_PIPELINES = [
'path.to.function1',
'path.to.function2',
...
]
-
Example 1: Show returned data from the OAuth request
settings.py
... SLACK_PIPELINES = [ 'my_app.pipelines.debug_oauth_request', ]
my_app/pipelines.py
def debug_oauth_request(request, api_data): print(api_data) return request, api_data
-
Example 2: Register User and send an email
settings.py
... SLACK_PIPELINES = [ 'my_app.pipelines.register_user', 'my_app.pipelines.send_email', ]
my_app/pipelines.py
from django.contrib.auth.models import User from django_slack_oauth.models import SlackUser def register_user(request, api_data): if api_data['ok']: user, created = User.objects.get_or_create( username=api_data['team_id']+':'+api_data['user_id'] ) if user.is_active: slacker, _ = SlackUser.objects.get_or_create(slacker=user) slacker.access_token = api_data.pop('access_token') slacker.extras = api_data slacker.save() if created: request.created_user = user return request, api_data def notify(request, api_data): if hasattr(request, 'created_user'): notify_admins("New user with id {} has been created.".format(request.created_user)) notify_user(request.created_user) return request, api_data
Thanks to Daniel van Flymen
The following parameters may be overriden, in the (rare) case that Slack changes their endpoints:
SLACK_AUTHORIZATION_URL = 'https://slack.com/oauth/authorize'
SLACK_OAUTH_ACCESS_URL = 'https://slack.com/api/oauth.access'
To avoid forgery attacks we pass the state
parameter in the initial authorization request. This state is stored in the session, which requires the session middleware to be enabled (on by default).