Popularity
3.7
Growing
Activity
4.3
Declining
12
1
10
Monthly Downloads: 4
Programming language: Elixir
License: MIT License
Tags:
Authentication
Latest version: v2.0.1
ueberauth_cas alternatives and similar packages
Based on the "Authentication" category.
Alternatively, view ueberauth_cas alternatives based on common mentions on social networks and blogs.
-
Pow
Pow is a robust, modular, and extendable authentication and user management solution for Phoenix and Plug-based apps. -
Shield
Shield is an OAuth2 Provider hex package and also a standalone microservice build top of the Phoenix Framework and 'authable' package. -
PowAssent
Use Google, Github, Twitter, Facebook, or add your custom strategy for authorization to your Pow enabled Phoenix app. -
ueberauth_facebook
Facebook OAuth2 Strategy for Überauth. -
ueberauth_identity
A simple username/password strategy for Überauth. -
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. -
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_active_directory
Uberauth strategy for Active Directory authentication. -
ueberauth_foursquare
Foursquare OAuth2 Strategy for Überauth.
Get performance insights in less than 4 minutes
Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
Sponsored
scoutapm.com
Do you think we are missing an alternative of ueberauth_cas or a related project?
README
Überauth CAS Strategy
Central Authentication Service strategy for Überauth.
Installation
- Add
ueberauth
andueberauth_cas
to your list of dependencies inmix.exs
:
def deps do
[
{:ueberauth, "~> 0.2"},
{:ueberauth_cas, "~> 2.0.0"}
]
end
- Ensure
ueberauth_cas
is started before your application:
def application do
[applications: [:ueberauth_cas]]
end
- Configure the CAS integration in
config/config.exs
:
config :ueberauth, Ueberauth,
providers: [cas: {Ueberauth.Strategy.CAS, [
base_url: "http://cas.example.com",
callback: "http://your-app.example.com/auth/cas/callback",
]}]
- 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.
Compatibility
Überauth CAS was tested with the Casino CAS server implementation. Please let me know if Überauth CAS is incompatible with your CAS server, and why.
The docs contain more information about protocol specifics.