Hi @ismcagdas
Thank you for your feedback. I understand. I'll try to play with since it's the business requirements. How can I change your current implementation to validate a unique email and username across tenants?
Regards Kasem
Hi,
I need your help to make the User a global entity (tenant unrelated). I still need multi-tenancy supported, but not for user (Users table). User needs to be without TenantId or at least disable user tenantId data filter (IMayHaveTenant) but also make username and email globally unique across tenants. Permissions should continue working tenant based and since you have TenantId in AbpRoles and AbpPermission I assume it should work with the desired change.
To better describe the problem, I need the same user/account (record) to exist in multiple tenants with different roles (not through linked accounts, but through AbpUserRoles). For example:
| UserId | TenantId | RoleId | | --- | --- | --- | | 1 | 1 | 1 | | 1 | 2 | 2 | | 1 | 2 | 3 |
I don't want the authentication to be affected by the current user tenant, selected through login, but rather make it a global authentication.
One of the solutions I thought about is having all users signin and signup in the Default tenant (statically set this) no matter in what tenant your session exists and also remove MayHaveTenant from User. Please let me know if this is applicable and how I can achieve the needed.
Thank you
Fixed now! thank you
Hi
I'll try but I had 9.1-rc1 downloaded last friday and I didn't see any changes in 9.1 stable release. How should I expect any fix now?
Although nothing was changed from RC1 to stable except version number it's magically fixed now!
How can I manually track history for entities I created before?
Ok. will try and update you
Thanks
Hi @ismcagdas
I noticed your official 9.1 version has just been released. Is the fix available already? if not when should I expect it?
Thanks
Hi @ismcagdas
The problem that my users can't use RememberMe option. Do you have other way to achieve the needed?
Thanks
Thank you.
I tried calling tryAuthWithRefreshToken in ZeroRefreshTokenService service but it didn't work since refreshToken cookie is always empty here. Please advice
I overrided CreateAsync to add a custom claim to user principal identity through UserClaimsPrincipalFactory and it works fine. I'm looking to modify this custom claim without relogin. I tried ReplaceClaimAsync method in UserManager and even called "await _signInManager.RefreshSignInAsync(user)" after updating claim but it didn't work. The claim modification is persisted in database but user session isn't affected until user relogin.