I am sure, that guys will upgrade. :) But look abp.io for your new projects. ;)
If connection string in appsettings.json would be encrypted for host database, how can system admin encrypt changed connection string and replace old one? For tenant it's simple, because C# logic makes encryption and decryption logic.
My response is for Volosoft (in consideration for better background jobs). :)
Having jobs in tenant's database would also have better performance impact on database. If there are a lot of tenants in system and background jobs in each tenants are frequent, thare could be a bottleneck on host database. Consider also this aspect.
I have question, because I do not completely understand how these timezone things are working. Currently, I have ANZ 6.3-based app (.NET Core + Angular 7 - moment 2.22.2, moment-timezone 0.5.23), but I belive that this applies identically to the latest version of ANZ. There is NO CHANGES for Clock provider (https://aspnetboilerplate.com/Pages/Documents/Timing) in Startup.cs (so "UnspecifiedClockProvider" is used), which I can confirm based on brakepoints in Application projects for Clock.Kind, Clock.SupportsMultipleTimezone and Clock.Provider values.
On dx-date-box (DevExtreme component), there is moment.Moment variable connected and when this variable is sent to backend (AppService) (completely unmodified in typescript), we can see UTC value for DateTime on C# side model (our thimezone is +2). So accepted value is 2 hours behind. However, I noticed, that this DateTime propery (on C# side) has property "Kind" value "Utc". https://docs.microsoft.com/en-us/dotnet/api/system.datetime.kind?view=netcore-2.2
So, how C# backed (DateTime propery in accepted model) has information about "Utc kind" of datetime (provided from moment.Moment variable on Angular side)?
including connection string or just tenantid value?
Sorry for late reply.
https://aspnetboilerplate.com/Pages/Documents/Abp-Session?searchKey=abpsession#overriding-current-session-values
Is changing tenantId database context also works inside using block?
using (_session.Use(42, null)) { //correct database context (connection string) for explicitly defined tenantId if this tenant has dedicated database (not using host database)? }
If I set ExpireDate (in AbpUserTokens table) manually for specific user (this kind of user is used for external system authentication which does NOT call Login and Logout method - just using bearer token which is generated by us (first login) and then ExpireDate is "manually corrected" to (very) distant future datetime).
Is this approach "stable and good enough) for life-long authentication? (I know that from a security perspective this is obviously very bad to have jwt token with a distant expiration date.)
My bad. :( I forgot that I did this once in the past.
Unfortunatelly, this does not work for ANZ 7.0 for Croatian (hr) language.
https://github.com/aspnetzero/aspnet-zero-core/issues/2451
Whole ANZ fallse back to En language.