|
1 | | -# authorizer |
2 | | - |
3 | | -authorizer is a complete open source authentication and authorization solution for your applications. Bring your database and have complete control over the authentication, authorization and user data. It is a microservice that can be deployed anywhere and connected any sql database. |
4 | | - |
5 | | -This an [Auth0](https://auth0.com) opensource alternative. |
6 | | - |
7 | | -Deploy authorizer Server with Postgres DB on Heroku and get a authorizer GraphQL endpoint in under 30 seconds |
8 | | - |
9 | | -[](https://heroku.com/deploy?template=https://github.com/authorizerdev/authorizer-heroku) |
11 | | - |
12 | | -## Features |
13 | | -### Flexible and easy to use |
14 | | -* Designed to work with any OAuth service, it supports OAuth 1.0, 1.0A and 2.0 |
15 | | -* Built-in support for many popular sign-in services |
16 | | -* Supports email / passwordless authentication |
17 | | -* Supports stateless authentication with any backend (Active Directory, LDAP, etc) |
18 | | -* Supports both JSON Web Tokens and database sessions |
19 | | -* Easy to deploy with docker, heroku |
20 | | -* Phase 1: supports postgres database |
21 | | -* SDKs for popular languages |
22 | | -* Quick frontend page library for (react, vue, svelete, vanilla) |
23 | | - |
24 | | -### Own your own data |
25 | | -* An open source solution that allows you to keep control of your data |
26 | | -* Supports Bring Your Own Database (BYOD) and can be used with any database |
27 | | -* Built-in support for Postgres |
28 | | - |
29 | | -### Secure by default |
30 | | -* Promotes the use of passwordless sign in mechanisms |
31 | | -* Designed to be secure by default and encourage best practice for safeguarding user data |
32 | | -* Uses Cross Site Request Forgery Tokens on POST routes (sign in, sign out) |
33 | | -* Default cookie policy aims for the most restrictive policy appropriate for each cookie |
34 | | -* When JSON Web Tokens are enabled, they are signed by default (JWS) with HS512 |
35 | | -* Use JWT encryption (JWE) by setting the option encryption: true (defaults to A256GCM) |
36 | | -* Auto-generates symmetric signing and encryption keys for developer convenience |
37 | | -* Attempts to implement the latest guidance published by Open Web Application Security Project |
38 | | -* Advanced options allow you to define your own routines to handle controlling what accounts are allowed to sign in, for encoding and decoding JSON Web Tokens and to set custom cookie security policies and session properties, so you can control who is able to sign in and how often sessions have to be re-validated. |
39 | | - |
40 | | -# License |
41 | | -[MIT](https://github.com/authorizerdev/authorizer/blob/main/LICENSE) |
42 | | - |
| 1 | +# authorizer |
0 commit comments