| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Cryptography has adopted a firefox-style versioning system where new
feature releases always have new major versions even if they don't have
backwards incompatible changes. This means that an upper bound on the
dependency does not make sense.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Bump pyjwt and cryptography versions
Bump PyJWT to v2. No backward incompatible changes in the new version
affects oauthlib.
Bump minimum cryptography version to 3. PyJWT bumps cryptography as
well plus older versions don't support newer versions of openssl.
* Remove python 3.5 support; add python 3.8 support
- Python 3.5 has reached end-of-life.
- Add support for Python 3.8
- Move dist to bionic (xenial is EOL in April)
- Upgrade pip in travis.yml's `before_install`. this should install a wheel
for pyca/cryptography
- Install rust for pypy builds. It is a requirement for cryptography as no
pypy wheels exist.
Co-authored-by: Asif Saif Uddin <auvipy@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
PyJWT helpers. Reformat some test certificates to be easier to maintain. Update documentation to match use of cryptography instead of PyCrypto
|
| |
|
|
| |
.travis.yml
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add a method to generate crypto tokens for use as Bearer tokens
* Add a method to verify an incoming crypto token and unpack the header and
claims
* Uses the PyJWT library
This is not JWT token support, merely a way to generate Bearer tokens that
won't have to be stored in a database but can self-validate and store
additional information that you see fit.
|
| | |
|
| | |
|
| | |
|
| |
|
