The LOG_LEVEL
can be set to (setting it to a value will also send logs of a higher value):
1
: Debug messages2
: Info messages3
: Errors4
: Critical errors
The LOG_TYPES
filter can be set to:
s
: Success Login (level: 1)seacft
: Success Exchange (level: 1)feacft
: Failed Exchange (level: 3)f
: Failed Login (level: 3)w
: Warnings During Login (level: 2)du
: Deleted User (level: 1)fu
: Failed Login (invalid email/username) (level: 3)fp
: Failed Login (wrong password) (level: 3)fc
: Failed by Connector (level: 3)fco
: Failed by CORS (level: 3)con
: Connector Online (level: 1)coff
: Connector Offline (level: 3)fcpro
: Failed Connector Provisioning (level: 4)ss
: Success Signup (level: 1)fs
: Failed Signup (level: 3)cs
: Code Sent (level: 0)cls
: Code/Link Sent (level: 0)sv
: Success Verification Email (level: 0)fv
: Failed Verification Email (level: 0)scp
: Success Change Password (level: 1)fcp
: Failed Change Password (level: 3)sce
: Success Change Email (level: 1)fce
: Failed Change Email (level: 3)scu
: Success Change Username (level: 1)fcu
: Failed Change Username (level: 3)scpn
: Success Change Phone Number (level: 1)fcpn
: Failed Change Phone Number (level: 3)svr
: Success Verification Email Request (level: 0)fvr
: Failed Verification Email Request (level: 3)scpr
: Success Change Password Request (level: 0)fcpr
: Failed Change Password Request (level: 3)fn
: Failed Sending Notification (level: 3)limit_wc
: Blocked Account (level: 4)limit_ui
: Too Many Calls to /userinfo (level: 4)api_limit
: Rate Limit On API (level: 4)sdu
: Successful User Deletion (level: 1)fdu
: Failed User Deletion (level: 3)
So for example, if I want to filter on a few events I would set the LOG_TYPES
filter to: sce,fce,scu,fcu
.
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
Auth0 helps you to:
- Add authentication with multiple authentication sources, either social like Google, Facebook, Microsoft Account, LinkedIn, GitHub, Twitter, Box, Salesforce, amont others, or enterprise identity systems like Windows Azure AD, Google Apps, Active Directory, ADFS or any SAML Identity Provider.
- Add authentication through more traditional username/password databases.
- Add support for linking different user accounts with the same user.
- Support for generating signed Json Web Tokens to call your APIs and flow the user identity securely.
- Analytics of how, when and where users are logging in.
- Pull data from other sources and add it to the user profile, through JavaScript rules.
- Go to Auth0 and click Sign Up.
- Use Google, GitHub or Microsoft Account to login.
This project is licensed under the MIT license. See the LICENSE file for more info.