Sample showing an invite only workflow. Users will not be able to sign-in, but provisioning will be managed by the (customer) administrators. A tutorial for this sample can be found at https://auth0.com/docs/tutorials/creating-invite-only-applications.
Read through the tutorial to understand how we're tuning Auth0 to prevent sign-ups and work with an invite-only workflow (through provisioning from the application's backend). In addition to that you'll need to specify your credentials and the connection in the Web.config
<!-- Auth0 Settings -->
<add key="auth0:ClientId" value="vg1EfxJRLmSqOmyclientid" />
<add key="auth0:ClientSecret" value="something-here-KgAlSCekALAkmM6zOK0dZ6chlzxnrWMnS9AIpapt5W" />
<add key="auth0:Domain" value="me.auth0.com" />
<add key="auth0:Connection" value="Username-Password-Authentication"/>
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.
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.
This project is licensed under the MIT license. See the LICENSE file for more info.