
Password migration by HTTP · Provider
Move passwords on the first sign-in
Users imported from a system that doesn't export password hashes have no password in Casdoor. On their first sign-in Casdoor asks the old system over HTTPS whether the password they typed is right, keeps it if it is, and never asks again.
https://auth.example.com with your Casdoor address (on Casdoor Cloud, something like https://acme.casdoor.com) and the other example.com addresses with your own.Set up Password migration by HTTP with Casdoor
- 1
Add the check to the old system
Expose an HTTPS endpoint that takes
POST {"username": "...", "password": "..."}with the bearer token you choose, and answers200 {"valid": true}when the password is right. - 2
Install the action
On the Marketplace page of the organization, install Password migration by HTTP. It needs a commercial edition license.
- 3
Turn it on
On the organization's Security tab, fill in these and save.
Password migration plugin Password migration by HTTP Password migration URL https://old.example.com/api/check-password Password migration secret the bearer token
Good to know
- The action can only reach the host of the migration URL, over HTTPS on port 443.
Password migration by HTTP settings are from its documentation as of November 2026 (OWASP: Authentication Cheat Sheet). Password migration by HTTP is a trademark of its owner.
More providers
View allAuthelia
OAuth providerLet people sign in to Casdoor through Authelia over OpenID Connect: the provider settings, and the client to add to Authelia's configuration.
authentik
OAuth providerLet people sign in to Casdoor with their authentik accounts over OpenID Connect: the provider settings, and the application and OAuth2 provider to create in authentik.
GitLab Self-Managed
OAuth providerLet people sign in to Casdoor with accounts on your own GitLab over OpenID Connect: the provider settings, and the OAuth application to create in GitLab.
