u/Ill-Ambassador-112

Projekat na kom radim ima jednu master bazu i tenant baze za svakog od tenanta (organizacija koje će koristiti softver). Namera mi je da imam jednu instancu aplikacije na jednom javnom domenu. Master baza sadrži tabelu sa svim korisnicima (iz svih tenanta) i preko nje ide login. U cookie se postavi claim tenantid i onda tako pri svakom requestu se dbcontext connection string i servis formiraju dinamički (pošto su scoped pa imamo tu dinamičnost), te se svaki korisnik rutira baš ka svojoj bazi. To sve lepo funkcionište, mene brine, kako se zaštiti od toga da neko slučajno se ne uloguje sa tuđim kredencijalima, osim uslovljavanja jakog passworda, šta bi još moglo da se preduzme kao mera zaštite? Hvala unapred.

I have db per tenant software. One DB for each Tenant, and one Master DB for universal stuff. All of users are stored in MasterUsers table (in Master DB). They have Username, Password, TenantId, TenantEmpId. TenantEmpId is connection to TenantUsers table which exist in every TenantDb. So i know for example user joe has masterempid 5 and tenantempid 3 for example. This way i can write documents and always put his tenantempd as foreign key in TenantTables. Since DB Context Service in .Net is Scoped per HTTP request i can form connection string dynamicaly. Only one thing that scares me here is what if someone accidentaly logs with credentials of user from other tenant...
I have one instance of application and one universal domain that everyone uses. I don't think my clients will have static servers that i could use to forward them to right channel. Did anyone have this use case and how to overcome this? Thanks in advance.

Da li neko zna u kojim intervalima ćemo imati dve trake iz NBG ka Zemunu a u kojim obrnuto?