Yandex OAuth2 strategy for Überauth.
-
Setup your application at Yandex Developer Console.
-
Add
:ueberauth_yandexto your list of dependencies inmix.exs:def deps do [{:ueberauth_yandex, "~> 0.1"}] end
-
Add the strategy to your applications:
def application do [applications: [:ueberauth_yandex]] end
-
Add Yandex to your Überauth configuration:
config :ueberauth, Ueberauth, providers: [ yandex: {Ueberauth.Strategy.Yandex, []} ]
-
Update your provider configuration:
config :ueberauth, Ueberauth.Strategy.Yandex.OAuth, client_id: System.get_env("YANDEX_CLIENT_ID"), client_secret: System.get_env("YANDEX_CLIENT_SECRET")
-
Include the Überauth plug in your controller:
defmodule MyApp.AuthController do use MyApp.Web, :controller plug Ueberauth ... end
-
Create the request and callback routes if you haven't already:
scope "/auth", MyApp do pipe_through :browser get "/:provider", AuthController, :request get "/:provider/callback", AuthController, :callback end
-
Your controller needs to implement callbacks to deal with
Ueberauth.AuthandUeberauth.Failureresponses.
For an example implementation see the Überauth Example application.
Depending on the configured url you can initiate the request through:
/auth/yandex
Or with options:
/auth/yandex?scope=login%3Aemail+login%3Ainfo+login%3Aavatar
By default the requested scope is "email". Scope can be configured either explicitly as a scope query value on the request path or in your configuration:
config :ueberauth, Ueberauth,
providers: [
yandex: {Ueberauth.Strategy.Yandex, [default_scope: "login:email login:info"]}
]To guard against client-side request modification, it's important to still check the domain in info.urls[:website] within the Ueberauth.Auth struct if you want to limit sign-in to a specific domain.
Sponsored by JetRockets.
Please see LICENSE for licensing details.
