cloudscribe | ASP.NET Core multi-tenant web application foundation with management for sites, users, roles, claims | Frontend Framework library

Every web application or website project tends to need a certain amount of basic functionality, why build this over and over?. If you start a new web application project in Visual Studio using the standard project templates, what you get is just a basic implementation for user accounts via ASP.NET Identity. Those templates don't provide you any method for creating administrative users or creating roles or managing users and user role membership. You would typically have to implement that stuff yourself, and if you are like me, you don't want to have to implement that stuff again and again on every project. cloudscribe.Core aims to provide that for you with careful, well thought out implementations that adhere to OWASP web security guidelines. To get started building your own features and applications with cloudscribe, please see our Introduction to learn about our project template for Visual Studio or the .NET Core CLI. See the full documentation at cloudscribe.com (work in progress). Introduction - get the big picture and learn how to start new projects using our project template for Visual Studio or the .NET Core CLI. Take a look at cloudscribe.SimpleContent, a simple yet flexible content and blogging engine that works with cloudscribe Core. We are collecting email addresses for a potential newsletter in the future, depending on whether this project becomes popular. If you would like to subscribe to this possible future newsletter, please send an email to subscribe [at] cloudscribe.com with the subject line "subscribe". If you are interested in consulting or other support services related to cloudscribe, please send an email to info [at] cloudscribe.com. We're also on twitter at @cloudscribeweb.
Login and registration, with support for social authentication configured from the UI. With options for recaptcha on the login and registration pages
Support for extra content on the login page
Support for extra content and a terms of use section on the registration page. If you populate the terms of use then users will be required to check a box indicating that they accept the terms in order to register and login. Also if you change the terms later you can optionally force all users to re-accept the changed terms.
User Management (optionally multi-tenant user management) you can create and manage user accounts, create and manage roles and user role membership, and add custom claims to users all from the UI. You can optionally disable self serve user registration so that only users that you add are allowed.
If you change a user's role membership, the role cookie will be updated automatically so the changes are effective right away.
If you lock a user account or delete a user, the user will be signed out automatically.
A theme system that supports both shared themes and per tenant themes. You can set the theme from a dropdown list in Administration > Site Settings, and the starter kits have a bunch of bootstrap themes included, and you can also make your own themes.
Support for "Site is Closed" - you can set a site as closed and users will not be able to navigate any pages in the site, they will only see the message you provide on the closed page. Users can still login but only members of the Administrators or Content Administrators roles will be allowed to navigate the site, all other users will be redirected to the closed message.
You can optionally require a confirmed email address for users if you add SMTP settings for email. A confirmation email will be sent to the user and the user will not be able to login until they click the link to confirm their email address.
You can optionally require approval of new accounts before a user can login, and you can get notification when new users register so you can decide whether to approve the account. There is a separate page to make it easy to find users who have not yet been approved or who have not yet confirmed their email address.
If you setup social authentication, you can optionally make social authentication the only allowed way to sign in.
You can configure SMS settings for Twilio, and then users can enable 2 factor authentication using their phone.
There is a company information section where you can define company name, address, email etc, and then you could show that information in the footer for example by customizing the layout. SiteContext is already injected into the layout and the company information are just properties on that so you can wrap your own markup around whichever of those properties you want to show.
Integration with IdentityServer4 providing management of users, clients and scopes. This brings us support for Jwt as an alternative to cookie authentication so we can more readily support SPA (Single Page Application) style web apps as well as authentication from mobile devices.
Optional LDAP Authentication support
Localization Support
For data access, supports Entity Framework Core with either SQLite, MSSQL, MySql, or PostgreSql. NoDb file system storage is also supported for small sites or proptypes.
Data and IO operations are async all the way down
This project aims to follow the OWASP Guidelines for best practices in security
Implement options for Security Questions and Answers per OWASP guidelines
Implement tracking of password hash history to support scenarios where re-using old passwords is not allowed
MongoDB Support - we are interested in trying to implement the data repositories with MongoDB and would welcome help with that.
Lots of miscellaneous smaller stuff