Replies: 8 comments 19 replies
-
|
I just saw this project while thinking about including "better ASP.NET Core authorization" in a new project. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @st1pps,
I have already decided that in version 2 roles that contain "advanced permissions" will not be available to a tenant admin. That removes the the issue of an tenant admin adding a role with powerful features to a tenant user. One other feature I had in the original "better ASP.NET Core authorization" code was a PaidForModules that allowed you register that certain Permissions are only available to a tenants that have bought that module (see diagram at the top of the old multi-tenant article). I haven't implemented that in the AuthP library as a) not many people use that, and b) its a bit clunky as you have to edit the Permissions code. If that's useful then I could add it to AuthP, but I would want a "contribution" (either you write the code and PR it, or I write the code for money😄) for that work . Finally a warning from my experience of designing a really big multi-tenant. My client has users that worked for different retail outlets, which meant that when a user that works in multiple retail outlets logged I had to provide a list of the retail outlets they were registered with so that when log in to the correct one. It was a pain to implement and I'm not planning to add it to the AuthP library. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @st1pps, I was thinking about your request and I'm not sure that having a tenant have their own roles. A SaaS (Multi-tenant) application is about providing the same service to many organizations. This suggests that there should be a global set of roles, which the tenant admin can add/remove to tenant users. I also think having roles linked to a tenant would make it very difficult for an overall admin user to work out any problems. The EF Core team are always talking about not adding features to the EF Core that could cause the developers to get into a bad situation. For this reason I won't be implementing a tenant-only role, but I think the PaidForModules is still relevant, as they are global way to manage the features available to users. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JonPSmith , |
Beta Was this translation helpful? Give feedback.
-
|
You have to understand that the library must provide a secure system for managing users, so I ensure that there are strong limits on what the tenant admin can do. That doesn't mean you can't write your own code, most likely using the various Admin services, to implement extra features for the tenant admin user. Its then up to you to make sure one tenant user can't change something they shouldn't have access to. You might find some of the extra features in version 2.0.0 of this library could help you. For instance I have implemented what I call 'tenant Roles' that can be added to a tenant such that each tenant can have optional versions. One use would have different versions of the app, say Free, Pro, Enterprise, and each tenant can pay for the higher levels. See issue #9 which describes this. NOTE: I released version 2.0.0 early because I found a critical bug in hierarchical multi-tenant in version 1. I will adding documentation and examples on the new multi-tenant features in the coming weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @st1pps, I have released an article called Multi-tenant apps with different versions can increase your profits that explains how the AuthP version 2.0.0 allows you to create Roles linked to a tenant. I think that is what you were asking for. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Thank you |
Beta Was this translation helpful? Give feedback.
-
|
In theory, yes, but I haven't tried it. A blazor webassembly still has a BUT the blazor webassembly doesn't support HostedSevices, which means you can't use AuthP's |
Beta Was this translation helpful? Give feedback.
-
|
Have you put any thought into supporting users with multiple roles? I've read the article series but haven't looked at the example app, so I don't know if it's already there. (Sorry) Use case: Imagine an inventory system targeted to small businesses. You'd probably have a role specific to filling orders (and, thus, decrementing your warehouse inventory) and a different role specific to restocking (incrementing) your warehouse inventory. If you only have a handful of employees, then the person doing the restocking will also probably be filling orders. Conceptually, people often wear multiple hats... have multiple roles. (I'm both a "developer" as well as "technical support".) I could have a single role that includes the permissions for both "hats", but I feel it's a better interpretation of the analogy to assign multiple "hats", multiple roles, to a single person. |
Beta Was this translation helpful? Give feedback.
-
|
Users can have multiple Roles. You should read the first article and look at the diagram at the top. You will see that the user has two Roles: Sales and FirstAid. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I like the AuthP library, but I miss the support of PostreSQL. Is it possible or planned extra feature to the next release? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @klasyc, PostgreSQL is in the roadmap, but a number of people have asked for sharding for multi-tenant applications. I plan to implement sharding first, then I will look at PostgreSQL. |
Beta Was this translation helpful? Give feedback.
-
|
Version 3.1.0 supports PostgreSQL |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JonPSmith I love this library very much. It's got a lot of things I've wanted in a multi-tenant application/ library. I would like to contribute to it, especially with enabling users to manage multiple the tenants. It seems you had some ideas already. How do you propose we communicate and so I can help? |
Beta Was this translation helpful? Give feedback.
-
|
@akema-trebla, come back to me with any suggestions before you actually change things as there are a few things to think about, e.g. adding more tests |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JonPSmith, Sorry for the late response. I've been unavailable for a while but I'm back now. I built a multi-tenant fashion designers' mobile app a few years ago and I decided to make it more scalable and easier to manage and that's when I found this project. I think it's a great productivity boost to have and I'd be honored to help in anyway I can. Does AuthP have a separate nuget package for the BaseCode? I'm asking because of DDD considerations. You can shoot me an email at [email protected]. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @akema-trebla,
The AuthP code is contained in multiple projects which all start with
You only need to set the AuthP's options with
I don't think an extra example of hierarchical tenant + sharding is worth the effort, as its just a mix of Example4 (hierarchical) and Example6 (Sharding). What are your skills - do they cover the front-end as well as a backend? An example of using Blazor Server with AuthP would be interesting. You could take Example4 (hierarchical) and create a new example that uses Blazor Server. That's a lot of work but a lot of people are asking how you would use AuthP with Blazor. If that is too much then I understand. |
Beta Was this translation helpful? Give feedback.
-
|
Alright. I'll work on the Blazor example. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @akema-trebla, That's great! Its quite a bit of work and a few things, like authorization in Blazor, will need some help from me. Can I suggest you open a new issue for this topic so we can confer on anything. I use issues when I find something I want to do and I might put down my thoughts (see issue #29) or to list the things I need to do (see issue #35). |
Beta Was this translation helpful? Give feedback.
-
|
Hello Jon, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nsfuntionality, The AuthP library provides a structure for building apps with administration features, but in normal use the AuthP code doesn't access the database because it uses claims. If you want to improve the performance of your application, then you need look at the code from your part of the application, e.g. Example3 provides a Invoice handler and that is the part that you need to apply caching, RabbitMQ or whatever to the part of your code. You might like to read my Five levels of performance tuning for an EF Core query article or chapters 14 to 16 in my book Entity Framework Core in Action for various ways to improve database-heavy applications. |
Beta Was this translation helpful? Give feedback.
-
|
I like this approach very much indeed. Did my own implementation for ongoing app development using ASP identity but your ideas are much better formed than mine so I'm switching to your plan. Some thoughts on Tenant Creation...
Hope that makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
Is there way we can have sub domain once the tenant is logged in? just like how we have navbar brand change to tenant name based on the login? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nsfuntionality,
I think you want the tenant name. The most straight way is to get the user's There is an AuthP feature called Another useful article is ASP.NET Core: Three(+1) ways to refresh the claims of a logged-in user, which gives some different approaches. |
Beta Was this translation helpful? Give feedback.
-
The AuthPermissions.AspNetCore library (shortened to AuthP) started with version 1.0.0, but many features have been added. This discussion is to get feedback on this library and what new features people would like.
REMEMBER: This is an open-source library which I work on in my "spare time", so don't expect me to produce new features quickly.
Version 9.0.0
Updates AuthP to .NET 9.
BREAKING CHANGE: EF Core 9 has added code to ensure that migrations are executed correctly - see EF Core 9's updated migrations. If you have build an multi-tenant application then you need to read the UpdateToVersion9 on how to update your app.
Version 8.0.0
Simplified to one NET type, in this case .NET 8. The changed makes it easier to update for future NET releases. See the "How to update a NuGet library once the author isn’t available" article for more information.
Version 6.2.1
Updated Net.RunMethodsSequentially to fix .NET 8 Postgres bug in the DistributedLock. See this section in the documentation about this feature.
Version 6.2.0
A small change to the Sign up for a new tenant, with versioning feature to handle fatal code problems, e.g.
Exceptions.This was because @akema-trebla had problems with errors (see issue #97). Once I got into I decided to redesign the code in the
SignInAndCreateTenantservice.Version 6.1.0
Version 6.0.0
See new Example7 app that provides an example of a multi-tenant application where every tenant has its own database. See the Sharding explained document about the new modes.
Version 5.0.0
SetupMultiTenantShardingthat sets up the sharding / hybrid multi-tenant feature. This makes it easier to set up this feature.SetupMultiTenantShardingextension method with your changes.Version 4.1.0
See Languages & cultures explained document to see what this new service provides.
Version 4.0.0
DataKeyof length of 250.Version 3.5.0
Small changes, some of which break existing projects but with very simple rename will fix it. Here is the changes
MarkJwtRefreshTokenAsUsedAsync(string userId)toLogoutUserViaRefreshTokenAsync(string refreshToken). See thelogoutWeb API in the AuthenticateController.LogoutUserViaUserIdAsync(string userId)that makes all the refresh token as invalid, so all logins for the user with the given userId will timeout.TenantChangeCookieEventtoSomethingChangedCookieEventIt also updates the Net.DistributedFileStoreCache to version 1.1.0, which is used in AuthP's Example2 (Web API app) to allow the claims in JWT Token to be changed. See articleASP.NET Core: Three ways to refresh the claims of a logged-in user for how this works (examples in the version 3.5.0 code).
Version 3.4.0
This contains one significant new feature and quite a few changes. The most important changes are:
New "down for maintenance" feature
This provides a multi-tenant app stop users accessing a tenant while its data is being changed, moved, e.g. moving a tenant's data from a shared database to its own database (sharding). This stops tenant data from being corrupted by a user while the move / change is running.
See the "Down for maintenance" feature documentation for more information.
Added timeout on user invitation
@idan-h said that the Invite new user feature should have a timeout on the invite sent to a person. This was added in this version and the Invite new user service documentation has been updated to show this.
Breaking change to the refresh users claims feature
The refresh users claims feature now uses the FileStore distributed database for better performance. The the updated Update claims on tenant change documentation shows how to add the FileStore distributed database feature.
Other changes
There are seven other changes in version 3.4.0 - see the ReleaseNotes for information on these changes.
Version 3.3.0
The main parts of version 3.3.0 is to create a generic version of the “invite a user” feature and the “sign up / versioning” features. This also requires two other supporting services:
This release also contains some bug fix #35 and improvement #39,
Version 3.2.0
A study of the version 3.0.0's sharding feature showed that it would very hard to manage multiple databases in production. This version solves this problem by using the
appsettingsfile's "ConnectionStrings" section to define the database servers and provides a newsharingssettings.jsonfile to manage the databases - see issue #29 for an overview of what is changed. New documentarian are:Other changes are:
UpdateUserAsyncnow allows you to select which properties you want to update - see docs: Admin -> AuthUser admin.andRemoveRoleToUseras the change to theUpdateUserAsync` covers this.Version 3.1.0
Version 3.0.0
BREAKING CHANGES - see this file for what you have to change
Limitations of these release
Possible extra features in next release, or future releases
OLD VERSIONS
Version 2.3.1
RoleType- see issue Multi-tenant Roles: Problem when changing a Roles RoleType or when deleting #13Version 2.2.0
New Feature: Added "Access the data of other tenant" feature - see issue #10
Version 2.1.0
This tidies up a few small issues found when writing the "Building ASP.NET Core and EF Core multi-tenant apps"articles. See ReleaseNotes for more info.
Version 2.0.0
First release of version 2 release of AuthPermissions. This was released early because I found a critical bug fix for hierarchical multi-tenant usage. See Migrate from AuthPermissions.AspNetCore 1.* to 2.0 for detailed information on how to upgrade to this version.
Summary of new features
Version 1.x.x
First release of the AuthPermissions.AspNetCore library, including three example applications.
Summary of main features
Limitations of this release
Beta Was this translation helpful? Give feedback.
All reactions