Casdoor is a UI-first Identity Access Management (IAM) / Single-Sign-On (SSO) platform based on OAuth 2.0, OIDC, SAML and CAS.
Casdoor serves both the web UI and the login requests from the application users.
Front-end and back-end separate architecture, developed by Golang, Casdoor supports high concurrency, provides web-based managing UI and supports multiple languages(Chinese, English).
Casdoor supports third-party applications login, such as GitHub, Google, QQ, WeChat, etc., and supports the extension of third-party login with plugins.
With Casbin based authorization management, Casdoor supports ACL, RBAC, ABAC, RESTful accessing control models.
Phone verification code, email verification code and password retrieval functions.
Accessing logs auditing and recording.
Alibaba Cloud, Tencent Cloud, Qiniu Cloud image CDN cloud storage.
Customizable registration, login, and password retrieval pages.
Casdoor supports integration with existing systems by db sync, so users can transition to Casdoor smoothly.
Casdoor supports mainstream databases: MySQL, PostgreSQL, SQL Server, etc., and supports the extension of new databases with plugins.
How it works:
Step 0 (Pre-knowledge)
- Casdoor's authorization process is built upon the OAuth 2.0 protocol, therefore it's highly recommended to take a brief look at how indeed does OAuth 2.0 works. An introduction to OAuth 2.0.
Step 1 (Authorization Request)
Your Application (could be a website or whatever) should compose an URL in this format
endpoint/login/oauth/authorize?client_id=xxx&response_type=code&redirect_uri=xxx&scope=read&state=xxx. In the URL replace
endpoint with your Casdoor's host URL, and replace
xxx with your own info.
How to fill out the
client_id: you can find this under each single Application
redirect_uri: you should set this to your own Application's callback URL, with this info, Casdoor can know where to send info back after authorization
state: you should fill this out with your Application name
The Application will speak to the user: "Hey, now I need some resources and I need your permission to take these resources, Do you mind going to this URL and filling out your username and password for me?"
With the correctly composed URL, your Application will make a user launch a request to this URL, and the
Authorization Request is done.
Step 2 (Authorization Grant)
This step is straightforward: the user is redirected to the URL composed above, and the user will see the login page from Casdoor. By typing the correct username and credential into the login page, Casdoor now knows the identity of the user, and is about to send two keywords:
state back to the callback URL set in Step 1.
The user opens the URL and provides the credentials to Casdoor. Casdoor will say: "Looking good ~ this is the user (who is authorizing the Application to get the
state) I know in my database, and I will send the
state back to the Application using the callback URL (
With these two keywords sent back to your Application, the authorization is now granted to the app, and thus
Authorization Grant is completed.
Casdoor also provides third-party logins, in this case, you will not see the credentials entry page but a list of third-party providers. You can login to your app using these providers, with Casdoor as a middle layer (middleware).
Step 3 (Authorization Grant)
In this step, your Application already has the code in hand from Step 2, and it will speak to Casdoor: "Hey, now the user agreed to give me the
code, do you wanna check this
code out and give me the
Step 4 (Access Token)
In this step, Casdoor speaks back to the Application: "You know what, this
code seems legit, you must be the right Application. Come here, it's the
access_token." With this
code, Casdoor knows that it is an authorized Application (authorization given by the correct user in Step 2) trying to get the
access_token (, which will be used later to get more useful things).
Step 5 (Access Token)
In this step, your Application says: "Nice one, just got the fresh-and-tasty
access_token, I can now use it to get something more valuable from the
And your Application turns to the
Resource Server: "Hey buddy, wanna check this
access_token out? I got this from Casdoor and do you want to see if this is the correct one you had with Casdoor?"
Step 6 (Protected Resource)
Resource Server speaks back to your Application: "Not bad ~ it seems just like the one I had with Casdoor, and Casdoor says whoever holds this
access_token can have these
Protected Resources. Now, you take it!"
And this is basically how Casdoor works with your Application.
Casdoor can play both
Authorization Server and
Resource Server parts, i.e. Casdoor authorizes our Application to get resources (e.g. usually the current logged in user's info) from Casdoor's database.
Here is an online demo deployed by Casbin.
Global admin login:
Casbin-OA is one of Casbin web apps. It uses Casdoor as authentication.
- Source code: https://github.com/casbin/casbin-oa
Casnode is the official forum developed by Casbin community.
It uses Casdoor as authentication platform and manage members.
- Source code: https://github.com/casbin/casnode
Casdoor contains 2 parts:
|Backend||RESTful API backend for Casdoor||Golang + Beego + SQL||https://github.com/casdoor/casdoor|