Patreon: https://levels.patreon.com/
Buffer: https://open.buffer.com/engineering-career-framework/
Rent the Runway: https://docs.google.com/document/d/1SxmQBrDZvj16veuc2OVO0wUX7a7vEKPM-57dNLXhuEk/edit
Medium: https://medium.com/s/engineering-growth-framework/engineering-growth-introduction-8ba7b78c8d6c
Kickstarter: https://gist.github.com/jamtur01/aef437a79fee5a9cefdc
| # -*- coding: utf-8 -*- | |
| from __future__ import unicode_literals | |
| from django.db import migrations, models | |
| from django_cryptography.fields import encrypt | |
| app_with_model = 'account' | |
| model_with_column = 'User' | |
| column_to_encrypt = 'email_address' | |
| column_field_class = models.CharField |
This configuration enables NGINX to validate an authentication token against an authorization server by using OAuth 2.0 Token Introspection (RFC 7662). This solution uses the auth_request module and the NGINX JavaScript module to require authentication and perform the token introspection request.
By default, the client's authentication token is expected as a bearer token supplied in the Authorization header. If supplied elsewhere in the HTTP request, the $access_token variable must be configured to specify where to obtain the token.
Token introspection requests are authenticated. By default, the $oauth_client_id and $oauth_client_secret variables are used to perform HTTP Basic authentication with the Authorization Server. If only the $oauth_client_secret variable is specified then that value is used
| import functools | |
| from django.conf import settings | |
| from django.db import transaction, utils | |
| def durable(func): | |
| """ | |
| Decorator to ensure that a function is not being called within an atomic block. |
