Application Config
After you deploy Casdoor on your server and set up your organization, you can now deploy your applications!
Let's see how to configure your application's authentication using Casdoor!
For example, I want to set up my Forum using Casnode.
I create my application and fill in some necessary configurations.
Select the organization I created so that users in this organization can use this application.

Since this organization is named my_organization, I choose it from the drop-down menu.

Next, I want my users to be able to use Casdoor for authentication when they sign up. So, I fill in the redirect URL here as https://your-site-url.com/callback.
Please note that the callback URL in the provider application should be Casdoor's callback URL, and the Redirect URL in Casdoor should be your website's callback URL.
Further Understanding
To make the authentication process work, the detailed steps are as follows:
- Users send a request to Casdoor.
- Casdoor uses the
Client IDandClient Secretto authenticate with GitHub, Google, or other providers. - If the authentication is successful, GitHub calls back to Casdoor to notify Casdoor about the successful authentication. Therefore, the GitHub authorization callback URL should be your Casdoor's callback URL, which is http://your-casdoor-url.com/callback.
- Casdoor then informs the application about the authentication success. This means that the Casdoor callback URL should be your application's callback URL, which is http://your-site-url.com/callback.
Verification Code Settings
You can configure the Code resend timeout to control how long users must wait before requesting another verification code via email or SMS. Set the value in seconds (default is 60). This helps prevent abuse while maintaining security. A value of 0 uses the global default.
If you want to do more personalized configuration of the application's sign-in methods, such as disabling a certain sign-in method or turning off a certain sign-in method, you can refer to the Signin Methods