Assent

Multi-provider authentication framework.

Features

• Includes the following base strategies:
  • OAuth 1.0 -Assent.Strategy.OAuth
  • OAuth 2.0 -Assent.Strategy.OAuth2
  • OpenID Connect -Assent.Strategy.OIDC
• Includes the following provider strategies:
  • Apple Sign In -Assent.Strategy.Apple
  • Auth0 -Assent.Strategy.Auth0
  • Azure AD -Assent.Strategy.AzureAD
  • Basecamp -Assent.Strategy.Basecamp
  • DigitalOcean -Assent.Strategy.DigitalOcean
  • Discord -Assent.Strategy.Discord
  • Facebook -Assent.Strategy.Facebook
  • Github -Assent.Strategy.Github
  • Gitlab -Assent.Strategy.Gitlab
  • Google -Assent.Strategy.Google
  • Instagram -Assent.Strategy.Instagram
  • LINE Login -Assent.Strategy.LINE
  • Linkedin -Assent.Strategy.Linkedin
  • Slack -Assent.Strategy.Slack
  • Stripe Connect -Assent.Strategy.Stripe
  • Twitter -Assent.Strategy.Twitter
  • VK -Assent.Strategy.VK

Installation

Add Assent to your list of dependencies inmix.exs:

defpdepsdo
[
#...
{:assent,"~> 0.2.4"},

# Required for SSL validation with:httpc adapter
{:certifi,"~> 2.4"},
{:ssl_verify_fun,"~> 1.1"}
]
end

Runmix deps.getto install it.

By default,:httpcwill be used for HTTP requests. To compile the app with:httpcsupport, please add:inetsto:extra_applicationsinmix.exs:

defapplicationdo
[
#...
extra_applications:[
#...
:inets
]
]
end

This is not necessary if you'll use another HTTP adapter, such as Mint.

Assent requires Erlang OTP 22.1 or greater.

Getting started

A strategy consists of two phases; request and callback. In the request phase, the user would normally be redirected to the provider for authentication, and then returned back to initiate the callback phase.

Single provider example

config=[
client_id:"REPLACE_WITH_CLIENT_ID",
client_secret:"REPLACE_WITH_CLIENT_SECRET",
redirect_uri:"http://localhost:4000/oauth/callback"
]

# Redirect user to provider
{:ok,%{url:url,session_params:session_params}}=
Assent.Strategy.Github.authorize_url(config)

# Handle callback
{:ok,%{user:user,token:token}}=
config
|>Assent.Config.put(:session_params,session_params)
|>Assent.Strategy.Github.callback(params)

Multi-provider example

This is a generalized flow that's similar to what's used inPowAssent.

config:my_app,:strategies,
github:[
client_id:"REPLACE_WITH_CLIENT_ID",
client_secret:"REPLACE_WITH_CLIENT_SECRET",
strategy:Assent.Strategy.Github
],
#...

defmoduleMultiProviderdo
@specrequest(atom())::{:ok,map()}|{:error,term()}
defrequest(provider)do
config=config!(provider)

config[:strategy].authorize_url(config)
end

@speccallback(atom(),map(),map())::{:ok,map()}|{:error,term()}
defcallback(provider,params,session_params\\%{})do
config=
provider
|>config!()
|>Assent.Config.put(:session_params,session_params)

config[:strategy].callback(config,params)
end

defpconfig!(provider)do
Application.get_env(:my_app,:strategies)[provider]||raise"No provider configuration for#{provider}"
end
end

Custom provider

You can add your own custom strategy.

Here's an example of an OAuth 2.0 implementation usingAssent.Strategy.OAuth2.Base:

defmoduleTestProviderdo
useAssent.Strategy.OAuth2.Base

@impltrue
defdefault_config(_config)do
[
site:"http://localhost:4000/api/v1",# The base URL to use for any paths below
authorize_url:"http://localhost:4000/oauth/authorize",# Full URL will not use the `:site` option
token_url:"/oauth/access_token",
user_url:"/user",
authorization_params:[scope:"email profile"],
auth_method::client_secret_post
]
end

@impltrue
defnormalize(_config,user)do
{:ok,
# Conformed to https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.5.1
%{
"sub"=>user["sub"],
"name"=>user["name"],
"nickname"=>user["username"],
"email"=>user["email"]
# },
# # Provider specific data not part of the standard claims spec
# %{
# "http://localhost:4000/bio" => user[ "bio" ]
}
}
end
end

The normalized user map should conform to theOpenID Connect Core 1.0 Standard Claims spec,and should return either{:ok, userinfo_claims}or{:ok, userinfo_claims, additional}.Any keys defined in the userinfo claims that aren't part of the specs will not be included in the user map. Instead, they should be set in the additional data that will then be merged on top of the userinfo claims excluding any keys that already been set.

You can also useAssent.Strategy:

defmoduleTestProviderdo
@behaviourAssent.Strategy

@specauthorize_url(Keyword.t())::{:ok,%{url:binary()}}|{:error,term()}
defauthorize_url(config)do
# Generate authorization url
end

@speccallback(Keyword.t(),map())::{:ok,%{user:map(),token:map()}}|{:error,term()}
defcallback(config,params)do
# Handle callback response
end
end

HTTP Adapter

By default Erlangs built-in:httpcis used for requests. SSL verification is automatically enabled when:certifiand:ssl_verify_funpackages are available.:httpconly supports HTTP/1.1.

If you would like HTTP/2 support, you should consider addingMintto your project.

Updatemix.exs:

defpdepsdo
[
#...
{:mint,"~> 1.0"},
{:castore,"~> 1.0"}# Required for SSL validation
]
end

Pass the:http_adapterwith your provider configuration:

config=[
client_id:"REPLACE_WITH_CLIENT_ID",
client_secret:"REPLACE_WITH_CLIENT_SECRET",
http_adapter:Assent.HTTPAdapter.Mint
]

JWT Adapter

By default the built-inAssent.JWTAdapter.AssentJWTis used for JWT parsing, but you can change it to any third-party library with a customAssent.JWTAdapter.AJOSEadapterAssent.JWTAdapter.JOSEis included.

To use JOSE, updatemix.exs:

defpdepsdo
[
#...
{:jose,"~> 1.8"}
]
end

And pass the:jwt_adapterwith your provider configuration:

config=[
client_id:"REPLACE_WITH_CLIENT_ID",
client_secret:"REPLACE_WITH_CLIENT_SECRET",
jwt_adapter:Assent.JWTAdapter.JOSE
]

LICENSE

(The MIT License)

Copyright (c) 2019-present Dan Schultzer & the Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.