tenancy | Automatic multi-tenancy for Laravel No code changes needed | Authorization library

I am using Oracle NoSQL Cloud Service on OCI and I want to write a program using the Oracle NoSQL Database Python SDK.

I did a test using the OCI SDK, I am using instance-principal IAM vs creating config files with tenancy/user ocid and API private keys on the nodes which invoke the noSQL api calls

Is it possible to do a connection using instance-principal instead of creating config files with tenancy/user ocid and API private keys with the Oracle NoSQL Database Python SDK.

I read the examples provided in the documentation https://github.com/oracle/nosql-python-sdk but I cannot find information about instance-principal support

I have an application I need to deploy that is requiring the App Registration to be "Accounts in any organizational directory (Any Azure AD directory - Multitenant)". What would the implication of setting this be? The application does not work if I set it to just "Accounts in this organizational directory only ( only - Single tenant)". The application using this App Registration is a Bot Framework application.

Where in the Bot framework code would there be some dependency on multi-tenancy? I would prefer to keep it as single tenant.

Thanks in advance, Jake.

There is a warning on the Firebase best practices documentation against using Firebase with multi-tenant applications: https://firebase.google.com/docs/projects/learn-more#multi-tenancy

This is what I am most concerned about: "Multi-tenancy can lead to serious configuration and data privacy concerns problems, including unintended issues with analytics aggregation, shared authentication, overly-complex database structures, and difficulties with security rules."

There is also plenty of official Google documentation supporting the use of Firebase for multi-tenancy, for instance: https://cloud.google.com/identity-platform/docs/multi-tenancy-authentication .

Do you know why they would have these conflicting recommendations and examples? Does use of Google Identity Platform fix the core security deficits mentioned in the warning?

I am re-posting this question, with additional clarification in the title, and a few edits/removals from the body, to specify that I am only looking for why this widely used product has this particular warning in its official documentation. I have removed most subjective content. I have no opinion on this that is relevant to the question - I am only looking to understand the warning. It seemed there was one good answer before the previous question was closed, so I will link that here for reference: Why is Google Firebase not recommended by Google in their own documentation for multi-tenant applications?

There is a warning on the Firebase best practices documentation against using Firebase with multi-tenant applications: https://firebase.google.com/docs/projects/learn-more#multi-tenancy

This is what I am most concerned about: "Multi-tenancy can lead to serious configuration and data privacy concerns problems, including unintended issues with analytics aggregation, shared authentication, overly-complex database structures, and difficulties with security rules." Identity Platform looks like it should cover everything except analytics aggregation and database structures, but I can control analytics logging and my database structure is simple enough, being divided cleanly by tenant. My application is one common application, but has tenanted client data and users (managed via Google Identity Platform).

There is also plenty of official Google documentation supporting the use of Firebase for multi-tenancy: https://cloud.google.com/identity-platform/docs/multi-tenancy-authentication . There are also dozens of examples out there for how to set up multi-tenancy with Firebase and Google Identity Provider.

Do you know why they would have these conflicting recommendations and examples? Does use of Google Identity Platform fix the core security deficits mentioned in the warning? It has me strongly considering abandoning Firebase, which would be a shame given the features it gives me.

I have the free developer E5 subscription and have setup a tenancy, created users etc. I have tried creating a second directory that I am planning to use to test the Azure AD Connect tool on a local server. I can switch between the tenants on the Azure Portal with the "Switch tenant" button however can't seem to figure it out with the Powershell cmdlets.

Connect-AzureAD

Set-AzContext -TenantId "My new tenant/directory"

Following these two commands is where the confusion starts. The first commands lists the users from the first directory and the second command shows the users from the directory I have switched too.

Get-AzureAdUser (Shows the first directory, not the one switched too)

Get-AzAdUser (Shows the users of the directory switched too)

Not sure if there is something I am missing here?

I am using this django_multitenant library to implement multi tenancy. I tried creating an object in python manage.py shell using the below code

We are working with a schema-based multi-tenancy database. We are on an Elixir stack, using Postgres, Ecto, and Triplex within a Phoenix Framework project.

We are using the default schema public to store common data, such as users and organisations. In particular, we have within the Organisations table a tenant_prefix column which we use to map a user to their tenancy.

Within a tenancy, we tenant-specific tables. As an example, we have a Products table. When a new organisation is created, we use Triplex to create the schema and run tenant migrations, which create the tenant-specific tables such as Products.

As a visual, the database looks like this:

I'm using this EC2 module with lite alteration to create EC2 instances and EBS volumes, Code is working without an issue, But I have requirement to add mount point as a tag in EBS, So I can use data filter to get that value and mount it using Ansible. Im trying to add tag value to "dynamic "ebs_block_device" through depoy-ec2.tf configuration file. As per the Terraform documentation tags is an optional value. Anyway, when I executing this it provided Unsupported argument error for tags value. Appreciate your support to understand issue here.

My Code as below.

Module main.tf

I am creating a subdomain-based multi-tenant laravel project using Tenancy For Laravel, everything is working fine except when trying to authenticate my API requests using Passport. How it works now is that I have a main database (multi-tenants) in which I declare tenants and specify the respective subdomain, and then each tenant has its own database (tenantfoo). I get through the Auth::check and credentials are checked in the correct database but when I try to create the token it stops using the tenant database (tenantfoo) and tries to create the token in the main database (multi-tenant) and gives the following exception.