2016-03-07 22:42:33 +11:00
Doorkeeper . configure do
# Change the ORM that doorkeeper will use (needs plugins)
orm :active_record
# This block will be called to check whether the resource owner is authenticated or not.
resource_owner_authenticator do
2016-08-27 03:12:19 +10:00
current_user || redirect_to ( new_user_session_url )
2016-03-07 22:42:33 +11:00
end
2017-09-28 07:42:49 +10:00
resource_owner_from_credentials do | _routes |
2020-01-03 15:35:46 +11:00
user = User . authenticate_with_ldap ( email : request . params [ :username ] , password : request . params [ :password ] ) if Devise . ldap_authentication
user || = User . authenticate_with_pam ( email : request . params [ :username ] , password : request . params [ :password ] ) if Devise . pam_authentication
2019-12-01 05:44:59 +11:00
if user . nil?
user = User . find_by ( email : request . params [ :username ] )
2020-01-03 15:35:46 +11:00
user = nil unless user & . valid_password? ( request . params [ :password ] )
2019-12-01 05:44:59 +11:00
end
2020-01-03 15:35:46 +11:00
user unless user & . otp_required_for_login?
2016-03-12 02:47:36 +11:00
end
2016-03-07 22:42:33 +11:00
# If you want to restrict access to the web interface for adding oauth authorized applications, you need to declare the block below.
2016-03-13 05:46:06 +11:00
admin_authenticator do
2017-09-28 07:42:49 +10:00
current_user & . admin? || redirect_to ( new_user_session_url )
2016-03-13 05:46:06 +11:00
end
2016-03-07 22:42:33 +11:00
# Authorization Code expiration time (default 10 minutes).
# authorization_code_expires_in 10.minutes
# Access token expiration time (default 2 hours).
# If you want to disable expiration, set this to nil.
2016-03-17 04:29:52 +11:00
access_token_expires_in nil
2016-03-07 22:42:33 +11:00
# Assign a custom TTL for implicit grants.
# custom_access_token_expires_in do |oauth_client|
# oauth_client.application.additional_settings.implicit_oauth_expiration
# end
# Use a custom class for generating the access token.
# https://github.com/doorkeeper-gem/doorkeeper#custom-access-token-generator
# access_token_generator "::Doorkeeper::JWT"
2017-08-05 12:24:58 +10:00
# The controller Doorkeeper::ApplicationController inherits from.
# Defaults to ActionController::Base.
# https://github.com/doorkeeper-gem/doorkeeper#custom-base-controller
base_controller 'ApplicationController'
2016-03-07 22:42:33 +11:00
# Reuse access token for the same resource owner within an application (disabled by default)
# Rationale: https://github.com/doorkeeper-gem/doorkeeper/issues/383
2017-04-27 22:42:22 +10:00
reuse_access_token
2016-03-07 22:42:33 +11:00
# Issue access tokens with refresh token (disabled by default)
# use_refresh_token
# Provide support for an owner to be assigned to each registered application (disabled by default)
# Optional parameter :confirmation => true (default false) if you want to enforce ownership of
# a registered application
# Note: you must also run the rails g doorkeeper:application_owner generator to provide the necessary support
2017-08-23 02:33:57 +10:00
enable_application_owner
2016-03-07 22:42:33 +11:00
# Define access token scopes for your provider
# For more information go to
# https://github.com/doorkeeper-gem/doorkeeper/wiki/Using-Scopes
2016-10-23 04:38:47 +11:00
default_scopes :read
2018-07-06 02:31:35 +10:00
optional_scopes :write ,
: 'write:accounts' ,
:'write:blocks' ,
2019-11-14 09:02:10 +11:00
:'write:bookmarks' ,
2018-10-19 10:47:29 +11:00
:'write:conversations' ,
2018-07-06 02:31:35 +10:00
:'write:favourites' ,
:'write:filters' ,
:'write:follows' ,
:'write:lists' ,
:'write:media' ,
:'write:mutes' ,
:'write:notifications' ,
:'write:reports' ,
:'write:statuses' ,
:read ,
:'read:accounts' ,
:'read:blocks' ,
2019-11-14 09:02:10 +11:00
:'read:bookmarks' ,
2018-07-06 02:31:35 +10:00
:'read:favourites' ,
:'read:filters' ,
:'read:follows' ,
:'read:lists' ,
:'read:mutes' ,
:'read:notifications' ,
:'read:search' ,
:'read:statuses' ,
:follow ,
2019-06-20 10:52:34 +10:00
:push ,
:'admin:read' ,
:'admin:read:accounts' ,
:'admin:read:reports' ,
:'admin:write' ,
:'admin:write:accounts' ,
2020-06-03 03:24:53 +10:00
:'admin:write:reports' ,
:crypto
2016-03-07 22:42:33 +11:00
# Change the way client credentials are retrieved from the request object.
# By default it retrieves first from the `HTTP_AUTHORIZATION` header, then
# falls back to the `:client_id` and `:client_secret` params from the `params` object.
# Check out the wiki for more information on customization
# client_credentials :from_basic, :from_params
# Change the way access token is authenticated from the request object.
# By default it retrieves first from the `HTTP_AUTHORIZATION` header, then
# falls back to the `:access_token` or `:bearer_token` params from the `params` object.
# Check out the wiki for more information on customization
# access_token_methods :from_bearer_authorization, :from_access_token_param, :from_bearer_param
# Change the native redirect uri for client apps
# When clients register with the following redirect uri, they won't be redirected to any server and the authorization code will be displayed within the provider
# The value can be any string. Use nil to disable this feature. When disabled, clients must provide a valid URL
# (Similar behaviour: https://developers.google.com/accounts/docs/OAuth2InstalledApp#choosingredirecturi)
#
# native_redirect_uri 'urn:ietf:wg:oauth:2.0:oob'
# Forces the usage of the HTTPS protocol in non-native redirect uris (enabled
# by default in non-development environments). OAuth2 delegates security in
# communication to the HTTPS protocol so it is wise to keep this enabled.
#
2016-10-01 06:40:31 +10:00
force_ssl_in_redirect_uri false
2016-03-07 22:42:33 +11:00
# Specify what grant flows are enabled in array of Strings. The valid
# strings and the flows they enable are:
#
# "authorization_code" => Authorization Code Grant Flow
# "implicit" => Implicit Grant Flow
# "password" => Resource Owner Password Credentials Grant Flow
# "client_credentials" => Client Credentials Grant Flow
#
# If not specified, Doorkeeper enables authorization_code and
# client_credentials.
#
# implicit and password grant flows have risks that you should understand
# before enabling:
# http://tools.ietf.org/html/rfc6819#section-4.4.2
# http://tools.ietf.org/html/rfc6819#section-4.4.3
#
2016-03-12 02:47:36 +11:00
grant_flows %w( authorization_code password client_credentials )
2016-03-07 22:42:33 +11:00
# Under some circumstances you might want to have applications auto-approved,
# so that the user skips the authorization step.
# For example if dealing with a trusted application.
2016-08-27 03:12:19 +10:00
skip_authorization do | resource_owner , client |
2016-10-03 07:55:09 +11:00
client . application . superapp?
2016-08-27 03:12:19 +10:00
end
2016-03-07 22:42:33 +11:00
# WWW-Authenticate Realm (default "Doorkeeper").
# realm "Doorkeeper"
end