ExFTP.Auth.BearerAuth (ExFTP v1.0.4)
View SourceWhen authenticator is ExFTP.Auth.BearerAuth
, this authenticator will call out to an HTTP endpoint that
implements Bearer Tokens
with the user's supplied credentials.
โ๏ธ Configuration
Keys
- authenticator ==
ExFTP.Auth.BearerAuth
- authenticator_config ::
ExFTP.Auth.BearerAuthConfig.t/0
Example
%{
# ... ,
authenticator: ExFTP.Auth.BearerAuth,
authenticator_config: %{
login_url: "https://httpbin.dev/bearer",
login_method: :post,
authenticated_url: "https://httpbin.dev/bearer",
authenticated_method: :post,
authenticated_ttl_ms: 1000 * 60 * 60
}
}
๐ See Also
๐ Resources
- ๐ RFC 959 (section-4)
- ๐ RFC 3659
- ๐ฌ Contact the maintainer (he's happy to help!)
Summary
Functions
Determines whether this session is still considered authenticated
Requests a login using a Bearer Token
Always returns true
.
Functions
@spec authenticated?(authenticator_state :: ExFTP.Authenticator.authenticator_state()) :: boolean()
Determines whether this session is still considered authenticated
๐ท๏ธ Params
- authenticator_state ::
ExFTP.Authenticator.authenticator_state/0
๐งโ๐ณ Workflow
- Reads the authenticator_config.
- If the config has authenticated_url,
- Calls it with a bearer token provided by the user in the headers
- If the response is HTTP 200, success. Otherwise, no longer authenticated.
- If the config does not have authenticated_url,
- investigate the authenticator_state for
authenticated: true
- investigate the authenticator_state for
โคต๏ธ Returns
โ On Success
`true` or `false`
๐ป Examples
iex> alias ExFTP.Auth.BearerAuth
iex> Application.put_env(:ex_ftp, :authenticator, ExFTP.Auth.BearerAuth)
iex> Application.put_env(:ex_ftp, :authenticator_config, %{
iex> login_url: "https://httpbin.dev/bearer",
iex> authenticated_url: "https://httpbin.dev/bearer",
iex> authenticated_method: :get,
iex> })
iex> BearerAuth.authenticated?(%{bearer_token: "my.bearer.token"})
true
๐ See Also
@spec login( provided_token :: ExFTP.Authenticator.password(), authenticator_state :: ExFTP.Authenticator.authenticator_state() ) :: {:ok, ExFTP.Authenticator.authenticator_state()} | {:error, term()}
Requests a login using a Bearer Token
๐ท๏ธ Params
- password ::
ExFTP.Authenticator.password/0
- authenticator_state ::
ExFTP.Authenticator.authenticator_state/0
๐งโ๐ณ Workflow
- Reads the authenticator_config.
- Receives a bearer token from the client (as a password)
- Calls the login_url with the proper bearer token headers
- If the response is HTTP 200, success. Otherwise, bad login.
โคต๏ธ Returns
โ On Success
{:ok, authenticator_state}
โ On Failure
{:error, bad_login}
๐ป Examples
iex> alias ExFTP.Auth.BearerAuth
iex> Application.put_env(:ex_ftp, :authenticator, ExFTP.Auth.BearerAuth)
iex> Application.put_env(:ex_ftp, :authenticator_config, %{
iex> login_url: "https://httpbin.dev/bearer",
iex> login_method: :post
iex> })
iex> {:ok, _} = BearerAuth.login("my.bearer.token" , %{})
๐ See Also
@spec valid_user?(username :: ExFTP.Authenticator.username()) :: boolean()
Always returns true
.
No performance benefit
This method is normally used to short-circuit bad login requests. The performance gain in that short-circuit is negligible for this authenticator, so it's not used.