pyoauth2: OAuth 2.0 Client and Provider Library
===============================================
Notice: this is not original package by @StartTheShift, but rather @Songbee's fork.
Supported Request Flows
-----------------------
(1) Authorization Code Grant :: OAuth 2 Section 4.1
(1A) Authorization Request :: OAuth 2 Section 4.1.1
[For browser apps this happens in the window]
Request: GET /get_authorization_code
?response_type=code
&client_id={CLIENT_ID}
&redirect_uri={REDIRECT_URI}
[&state={STATE}]
[&scope={SCOPE}]
Response: HTTP 302
Location={REDIRECT_URI}
?code={CODE}
&state={STATE}
Error Response: HTTP 302
Location={REDIRECT_URI}
?error=access_denied
&state={STATE}
(1B) Access Token Request :: OAuth 2 Section 4.1.3
[Server side only]
Request: GET /get_access_token
?grant_type=authorization_code
&client_id={CLIENT_ID}
&client_secret={CLIENT_SECRET}
&redirect_uri={REDIRECT_URI}
&code={CODE}
Response: HTTP 200
{
"access_token": "{ACCESS_TOKEN}",
"token_type": "{TOKEN_TYPE}", // See OAuth 2 Section 7.1 Access Token Types
"expires_in": 3600,
"refresh_token": "{REFRESH_TOKEN}"
}
Error Response: HTTP 400
{
"error": "access_denied",
"error_description": "User does not have access to the team."
}
===============================================
Notice: this is not original package by @StartTheShift, but rather @Songbee's fork.
Supported Request Flows
-----------------------
(1) Authorization Code Grant :: OAuth 2 Section 4.1
(1A) Authorization Request :: OAuth 2 Section 4.1.1
[For browser apps this happens in the window]
Request: GET /get_authorization_code
?response_type=code
&client_id={CLIENT_ID}
&redirect_uri={REDIRECT_URI}
[&state={STATE}]
[&scope={SCOPE}]
Response: HTTP 302
Location={REDIRECT_URI}
?code={CODE}
&state={STATE}
Error Response: HTTP 302
Location={REDIRECT_URI}
?error=access_denied
&state={STATE}
(1B) Access Token Request :: OAuth 2 Section 4.1.3
[Server side only]
Request: GET /get_access_token
?grant_type=authorization_code
&client_id={CLIENT_ID}
&client_secret={CLIENT_SECRET}
&redirect_uri={REDIRECT_URI}
&code={CODE}
Response: HTTP 200
{
"access_token": "{ACCESS_TOKEN}",
"token_type": "{TOKEN_TYPE}", // See OAuth 2 Section 7.1 Access Token Types
"expires_in": 3600,
"refresh_token": "{REFRESH_TOKEN}"
}
Error Response: HTTP 400
{
"error": "access_denied",
"error_description": "User does not have access to the team."
}
Metadata
Release files for pyoauth2-shift 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyoauth2-shift-0.0.1.tar.gz | 9.1 kB | Without provenance | Details |
Release files / pyoauth2-shift-0.0.1.tar.gz
| Download URL | pyoauth2-shift-0.0.1.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c23e4f331157cfb04d95bf43d02643721dc01a93c9b705dc5e6cd1c14709be58
|
|
BLAKE2b-256 checksum How to use checksums |
520cf43abc8a59604925fbd9446ed277ae9d08167bc055a70db00e25138c6248
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyoauth2-shift 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.