This guide helps you trying out Authorizer and evaluate it. It includes instructions for installing the Authorizer server in standalone mode.
Deploy production ready Authorizer instance using one click deployment options available below
|Infra provider||One-click link||Additional information|
For more information check docs
- Open authorizer instance endpoint in browser
- Sign up as an admin with a secure password
- Configure environment variables from authorizer dashboard. Check env docs for more information
DATABASE_NAMEare only configurable via platform envs
- For social logins, you will need respective social platform key and secret
- For having verified users, you will need an SMTP server with an email address and password using which system can send emails. The system will send a verification link to an email address. Once an email is verified then, only able to access it.
Note: One can always disable the email verification to allow open sign up, which is not recommended for production as anyone can use anyone's email address 😅
- For persisting user sessions, you will need Redis URL (not in case of railway app). If you do not configure a Redis server, sessions will be persisted until the instance is up or not restarted. For better response time on authorization requests/middleware, we recommend deploying Redis on the same infra/network as your authorizer server.
This example demonstrates how you can use
@authorizerdev/authorizer-js CDN version and have login ready for your site in few seconds. You can also use the ES module version of
@authorizerdev/authorizer-js or framework-specific versions like
Note: Change AUTHORIZER_URL in the below code with your authorizer URL. Also, you can change the logout button component