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.
-
guardian
An authentication framework for use with Elixir applications. -
coherence
Coherence is a full featured, configurable authentication system for Phoenix. -
ueberauth
An Elixir Authentication System for Plug-based Web Applications. -
Pow
Pow is a robust, modular, and extendable authentication and user management solution for Phoenix and Plug-based apps. -
phx_gen_auth
An authentication system generator for Phoenix 1.5 applications. -
Phauxth
Authentication library for Phoenix, and other Plug-based, web applications -
Shield
Shield is an OAuth2 Provider hex package and also a standalone microservice build top of the Phoenix Framework and 'authable' package. -
goth
OAuth 2.0 library for server to server applications via Google Cloud APIs. -
PowAssent
Use Google, Github, Twitter, Facebook, or add your custom strategy for authorization to your Pow enabled Phoenix app. -
basic_auth
Elixir Plug to easily add HTTP basic authentication to an app. -
ueberauth_facebook
Facebook OAuth2 Strategy for Überauth. -
aws_auth
AWS Signature Version 4 Signing Library for Elixir. -
doorman
Tools to make Elixir authentication simple and flexible. -
ueberauth_auth0
An Ueberauth strategy for using Auth0 to authenticate your users. -
ueberauth_identity
A simple username/password strategy for Überauth. -
Paseto
An Elixir implementation of Paseto (Platform-Agnostic Security Tokens) -
elixir_auth_google
The simplest way to add Google OAuth authentication ("Sign in with Google") to your Elixir/Phoenix app. -
passwordless_auth
Simple passwordless login or 2-factor / multi-factor authentication for Elixir. -
blackbook
All-in-one membership/authentication system for Elixir. -
aeacus
A simple configurable identity/password authentication module (Compatible with Ecto/Phoenix). -
phoenix_client_ssl
Client SSL Authentication Plugs for Phoenix and other Plug-based apps. -
ueberauth_cas
Central Authentication Service strategy for Überauth. -
ueberauth_active_directory
Uberauth strategy for Active Directory authentication. -
zachaeus
An easy to use licensing system, based on asymmetric cryptography. -
exBankID
exBankID is a simple stateless API-client for the Swedish BankID API -
sesamex
Another simple and flexible authentication solution in 5 minutes!. -
sigaws
AWS Signature V4 signing and verification library (Doc). -
oauth2_facebook
A Facebook OAuth2 Provider for Elixir. -
apache_passwd_md5
Apache/APR Style Password Hashing. -
ueberauth_foursquare
Foursquare OAuth2 Strategy for Überauth.
Scout APM - Leading-edge performance monitoring starting at $39/month
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.