multi-tenant | tenancy Implementation Demo of Spring boot | Object-Relational Mapping library

I acquired the oauth2 token using the usual workflow via golang.org/x/oauth2 but can't authenticate graph sdk (github.com/microsoftgraph/msgraph-sdk-go). My app allows both multi-tenant AD and personal accounts.

I implemented azcore.TokenCredential interface:

I'm working on the multi-tenant application and each user has its database.
Assume we have more tenants and each tenant has schema (schema1, schema2, schema3,....)
and each schema has the same structure of tables.
Each schema has a customer table with the same structure(id, name, age,...).
I have a table called tenants in the shared schema (shared_schema) that has all schema names in a column called tenant_id.
So how can get all schema from tenants table and then get customer count for each schema
in single (query, procedure, view,... any workaround).

tenants table:-

schema1, schema2,....
customer table

Expected result

procedure workaround

In a multi-tenant ABP MVC app, there is a built-in endpoint to list users:

GET: /api/identity/users

This endpoint only shows users belonging to the Current Tenant.

Is there a way to ignore the multi-tenancy filter as the 'host admin', to list all users, across all tenants?

Similarly, can the 'host admin' create/ modify/ delete users in other tenants via the same api/identity/users endpoint?

Or is writing a custom endpoint the only way?

I'm running Airflow v2.2.3 on Kubernetes.

I have a dedicated scheduler pod, a dedicated web-server pod and I'm using Kubernetes Executors.

I have ~4,000 DAGs, created dynamically in a for-loop.

I read Astronomer's post about "fast-follow" (also called "mini-scheduler") and I wonder if there's an option to disable it via configuration or something.

The thing is, that it comes with a penalty where:

• Dynamic DAGs are being calculated per each task operator, as a new fresh executor is running every time - I never saw reuse of Kubernetes executor (and if it using pod's patch verb for that - I guess that the dynamic DAGs would recalculated again anyway).
• The time it takes to recalculate dynamic DAGs lead to a "queued" status for every task - which mean that a lot of time is spent just for recalculating the DAGs over and over again.

1. Is there a configuration (or any other way) to disable the mini-scheduler?
2. Am I using the KubernetesExecutor wrong? should it stay up for more than one task (and thus calculate the dags only at the beginning)
3. I'm running a multi-tenant setup, where each one of my customers (businesses) run it's own DAG - but they all look the same (except input arguments + schedule time). Should I take a different approach? (other than using a dedicated DAG per customer).

Thanks

I don't do much web work but I recently began using FastAPI and am building an MVC app with jinja2 templating that uses PowerBI embedded capacity to serve multiple embedded analytics in app owns data arrangement. All of this works beautifully. However, I'm wanting to add further modules and I'd like to use the msal package to do user authentication by routing a user to the Microsoft login page, letting them sign in against a multi-tenant app service I set up in Azure, and then redirecting back to my page via redirect URI, grabbing the token, and progressing with authorization. Microsoft saved a great example our here for doing this in Flask. However, I am having fits porting the example to FastAPI.

I can get the user to the login screen and log in but I am having no luck capturing the token at my call back URI - it's appropriately routing but I am unable to capture the token from the response.

Has anyone (or can anyone) taken that super simple Flask example and ported it to FastAPI? Everything I find online for FAPI is back-end token-bearer headers for APIs - not meant for MVC apps.

Here's my current code. Messy because I have "tests" built in.

I was wondering how to Override the Identity Management Module to Work with Multi-tenant Web-Apps in Abp Framework . I want to Make my newly registered Users to become the admin of their own tenant and be able to Manage (Crud + Permission / Role Management ) their Subset users? For now I've created a custom UI to manage them, but I'm curios if it's possible to configure the Identity Management Module to do the job?

I'm trying to implement a hierarchical structure using the InheritanceType.JOINED approach to store data in hierarchical DB tables. One caveat is that in our multi-tenant solution, a tenant_id column needs to be present on every table (for security and legal export reasons), even though this is redundant in some cases. This requirement is fixed.

Issue is that when inserting data, the query Hibernate generates does not fill in the tenant_id on the parent- and childtable, causing a constraint error.

The tables in the DB would look like this:

Code for the abstract vehicle entity:

I have a multi-tenant application and the backend comprises of the microservices. The tenant admin will have a preferences page on the UI that can store system preferences for the tenant (i.e all users of the tenant).

I am thinking about what the best place for storing this would be?

SSM or Dynamo? Any trade-offs here for this use case?

we have a tenant microservice or we could create a system preferences microservice to store the preferences. I am trying to avoid all cross-service communication so the user of each tenant will get all the preferences on login and will send them back in the header. Should we continue to store the preferences in the tenant DB or system preferences microservice is the way to go?

I have a Spring Boot 2 + Hibernate 5 Multi-tenant application that connected to multiple oracle databases. when I use JpaRepository, everything is fine, ie after recieving http request, the 'Interceptor' detects the data source and the 'MultiTenantConnectionProvider' implementation selects the correct DataSource to be used by TransactionManager. What is the problem? I want to use TransactionInterceptor to handle transactions on some methods(with method names) from specific beans(that extends JdbcDaoSupport or inject JdbcDaoSupport implementations). Sorry if I explained a little confusing. But for every http request, the data source of that beans is immutable(the default data source). while injected repositories operate on the correct data source within the correct transaction.