Pre-set Configurations
Flask-Dance comes with pre-set OAuth consumer configurations
for a few popular OAuth providers. If you want to use Flask-Dance with an
OAuth provider that isn’t listed here, simply create an instance of
OAuth1ConsumerBlueprint or
OAuth2ConsumerBlueprint
and provide the information for your provider. We also welcome pull requests
to add new pre-set configurations to Flask-Dance!
Github
-
flask_dance.contrib.github.make_github_blueprint(client_id=None, client_secret=None, scope=None, redirect_url=None, redirect_to=None, login_url=None, authorized_url=None, session_class=None)[source]
Make a blueprint for authenticating with Github using OAuth 2. This requires
a client ID and client secret from Github. You should either pass them to
this constructor, or make sure that your Flask application config defines
them, using the variables GITHUB_OAUTH_CLIENT_ID and GITHUB_OAUTH_CLIENT_SECRET.
Parameters: |
- client_id (str) – The client ID for your application on Github.
- client_secret (str) – The client secret for your application on Github
- scope (str, optional) – comma-separated list of scopes for the OAuth token
- redirect_url (str) – the URL to redirect to after the authentication
dance is complete
- redirect_to (str) – if redirect_url is not defined, the name of the
view to redirect to after the authentication dance is complete.
The actual URL will be determined by flask.url_for()
- login_url (str, optional) – the URL path for the login view.
Defaults to /github
- authorized_url (str, optional) – the URL path for the authorized view.
Defaults to /github/authorized.
- session_class (class, optional) – The class to use for creating a
Requests session. Defaults to
OAuth2Session.
|
Return type: | OAuth2ConsumerBlueprint
|
Returns: | A blueprint to attach to your Flask app.
|
-
flask_dance.contrib.github.github
A LocalProxy to a requests.Session that
already has the Github authentication token loaded (assuming that the user
has authenticated with Github at some point in the past).
Google
-
flask_dance.contrib.google.make_google_blueprint(client_id=None, client_secret=None, scope=None, offline=False, redirect_url=None, redirect_to=None, login_url=None, authorized_url=None, session_class=None)[source]
Make a blueprint for authenticating with Google using OAuth 2. This requires
a client ID and client secret from Google. You should either pass them to
this constructor, or make sure that your Flask application config defines
them, using the variables GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET.
Parameters: |
- client_id (str) – The client ID for your application on Github
- client_secret (str) – The client secret for your application on Github
- scope (str, optional) – comma-separated list of scopes for the OAuth token.
Defaults to the “profile” scope.
- offline (bool) – Whether to request offline access
for the OAuth token. Defaults to False
- redirect_url (str) – the URL to redirect to after the authentication
dance is complete
- redirect_to (str) – if redirect_url is not defined, the name of the
view to redirect to after the authentication dance is complete.
The actual URL will be determined by flask.url_for()
- login_url (str, optional) – the URL path for the login view.
Defaults to /google
- authorized_url (str, optional) – the URL path for the authorized view.
Defaults to /google/authorized.
- session_class (class, optional) – The class to use for creating a
Requests session. Defaults to
OAuth2Session.
|
Return type: | OAuth2ConsumerBlueprint
|
Returns: | A blueprint to attach to your Flask app.
|
-
flask_dance.contrib.google.google
A LocalProxy to a requests.Session that
already has the Google authentication token loaded (assuming that the user
has authenticated with Google at some point in the past).
JIRA
-
flask_dance.contrib.jira.make_jira_blueprint(base_url, consumer_key=None, rsa_key=None, redirect_url=None, redirect_to=None, login_url=None, authorized_url=None, session_class=None)[source]
Make a blueprint for authenticating with JIRA using OAuth 1. This requires
a consumer key and RSA key for the JIRA appication link. You should either
pass them to this constructor, or make sure that your Flask application
config defines them, using the variables JIRA_OAUTH_CONSUMER_KEY and
JIRA_OAUTH_RSA_KEY.
Parameters: |
- base_url (str) – The base URL of your JIRA installation. For example,
for Atlassian’s hosted OnDemand JIRA, the base_url would be
https://jira.atlassian.com
- consumer_key (str) – The consumer key for your Application Link on JIRA
- rsa_key (str or path) – The RSA private key for your Application Link
on JIRA. This can be the contents of the key as a string, or a path
to the key file on disk.
- redirect_url (str) – the URL to redirect to after the authentication
dance is complete
- redirect_to (str) – if redirect_url is not defined, the name of the
view to redirect to after the authentication dance is complete.
The actual URL will be determined by flask.url_for()
- login_url (str, optional) – the URL path for the login view.
Defaults to /jira
- authorized_url (str, optional) – the URL path for the authorized view.
Defaults to /jira/authorized.
- session_class (class, optional) – The class to use for creating a
Requests session. Defaults to
OAuth1Session.
|
Return type: | OAuth1ConsumerBlueprint
|
Returns: | A blueprint to attach to your Flask app.
|
-
flask_dance.contrib.jira.jira
A LocalProxy to a requests.Session that
already has the JIRA authentication token loaded (assuming that the user
has authenticated with JIRA at some point in the past).