ueberauth_microsoft alternatives and similar packages
Based on the "Authentication" category.
Alternatively, view ueberauth_microsoft alternatives based on common mentions on social networks and blogs.
-
Phauxth
Not actively maintained - Authentication library for Phoenix, and other Plug-based, web applications -
Shield
DISCONTINUED. Shield is an OAuth2 Provider hex package and also a standalone microservice build top of the Phoenix Framework and 'authable' package. -
elixir_auth_google
👤Minimalist Google OAuth Authentication for Elixir Apps. Tested, Documented & Maintained. Setup in 5 mins. 🚀 -
aeacus
A simple, secure, and highly configurable Elixir identity [username | email | id | etc.]/password authentication module to use with Ecto. -
zachaeus
An easy to use licensing system, using asymmetric cryptography to generate and validate licenses.
WorkOS - The modern identity platform for B2B SaaS
Do you think we are missing an alternative of ueberauth_microsoft or a related project?
README
Überauth Microsoft
Microsoft OAuth2 strategy for Überauth.
Installation
Setup your application at the new Microsoft app registration portal.
Add
:ueberauth_microsoft
to your list of dependencies inmix.exs
:def deps do [{:ueberauth_microsoft, "~> 0.8"}] end
Add the strategy to your applications:
def application do [applications: [:ueberauth_microsoft]] end
Add Microsoft to your Überauth configuration:
config :ueberauth, Ueberauth, providers: [ microsoft: {Ueberauth.Strategy.Microsoft, []} ]
Update your provider configuration:
config :ueberauth, Ueberauth.Strategy.Microsoft.OAuth, client_id: System.get_env("MICROSOFT_CLIENT_ID"), client_secret: System.get_env("MICROSOFT_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.Auth
andUeberauth.Failure
responses.
For an example implementation see the Überauth Example application.
Single Tenancy
If you are going to use your app only internally you may need to configure it for a single tenant.
To do so you only need to add tenant_id
to your provider configuration like:
config :ueberauth, Ueberauth.Strategy.Microsoft.OAuth,
tenant_id: System.get_env("MICROSOFT_TENANT_ID"),
client_id: System.get_env("MICROSOFT_CLIENT_ID"),
client_secret: System.get_env("MICROSOFT_CLIENT_SECRET")
Calling
Depending on the configured url you can initial the request through:
/auth/microsoft
By default the scopes used are
- openid
- offline_access
- https://graph.microsoft.com/user.read
Note: at least one service scope is required in order for a token to be returned by the Microsoft endpoint
You can configure additional scopes to be used by passing the extra_scopes
option into the provider
config :ueberauth, Ueberauth,
providers: [
microsoft: {Ueberauth.Strategy.Microsoft, [extra_scopes: "https://graph.microsoft.com/calendars.read"]}
]
License
Please see LICENSE for licensing details.
*Note that all licence references and agreements mentioned in the ueberauth_microsoft README section above
are relevant to that project's source code only.