fido | Teaching old shellcode new tricks

I've this data:

I've this dataset:

Found a few postings on this, but none with a solution which solves what I am looking for. I am trying to import an excel file and save it as JSON, but group up some columns under others in the JSON file.

Here is my excel data:

Here is my python code:

Suppose I have this dataset:

In the ValidationResult that I get when readying my app for submission to the Microsoft Store (which my app "PASSED WITH WARNINGS") , I got this "Fail" under the "Package Sanity Test" section of the report:

I find this confusing, as it says both that "e_sqlite3.dll is designed only for arm processor type" AND that "e_sqlite3.dll is designed only for x64 processor type"

Shouldn't the word "only" preclude multiple statements of that type? Would it make sense for me to say, "My only dog is named Fido" AND "My only dog is named Spot"?

And besides, after complaining that "e_sqlite3.dll is designed only for x64 processor type," the message "admits" that ProcessorArchitecture is, indeed, declared as being x86 in that case. So what's the problem?

I find it odd that this is classified as a failed part of the test, yet the overall results are that my app passed (albeit with warnings).

Here are the Configuration Manager settings for this solution:

What do I need to do, if deploying the app as-is will cause SQLite to not run on some users' machines?

To answer Peter Torr's questions, here are the SQLite references in the project:

All of my SQLite-related usings are:

Below is a table I have created using the Reportlab library, specifically the SimpleDocTemplate from reportlab.platypus:

I'm facing the following problem with wso2 IS: I'm trying to register a service provider for all the tenants to access.

If using SaaS app I will be able to use the flow defined by the tenant that registered the service provider. However I need to configure the flow for each tenant. (Just the local authentication, inbound is oidc/oauth2 for all of them)

I tried creating a service provider (SP) for each tenant. Problem is that I’ll have a different client_id (oidc/oauth2 code flow).

Shouldn’t client_id be modifiable?

I found out that I can set the client_id if creating the SP from a file. Then I discovered another problem. If I try to use the same client_id twice (on different tenants) I get an error creating the SP. I managed to overcome this issue by manually changing the H2 database. However it does not work. I specify tenanDomain url parameter but it’s ignored, it uses the first sp for that client_id found in the database.

Shouldn’t this selection be tenant dependent?

I’ve read that I can achieve this using SAML, however it’s not ideal for a SPA.

Finally, there are two solutions. But they are far from ideal, as both require manual steps:

1. Use adaptive authentication, then I need to register all tenant IdP in the SaaS app tenant and in the script.

2. Create a tenant/client_id relation in the app, then update it whenever there is a new service provider registration for that app on any tenant.

I think this is a valid use case. Am I right?

Is there any way to achieve this behavior without the proposed functional modifications?

Update: Full use case explanation

The use case is the following. I have a microservices application, I want to use wso2is to provide identity to the users of that application. In the application I have a customer (which has many users). A customer is assigned to a tenant. I want the customer admin (tenant admin) to be able to manage some aspects of its tenant identity, like password policies, users... However, I don't want the tenant to register applications (service providers), so I need to register the application so that any customer (tenant) can access it. I need the authentication flow for that application to be defined tenant-wise. I don't want to impose authentication policies on any tenant, they should be able to impose their own policies. To do that they'll have two ways:

1. They can choose to use wso2is to define the flow they want (basic, risk based, fido...).
2. To use a third party (federated IdP), therefore setting login policies there.

I'll also need the super-tenant (me, or a specific user created to assist a concrete tenant) to be able to access all other tenants, for example to provide assistance, fix mistakes, and disable functionality I don't want them to see like (e-mail templates).

I'm trying to figure this out in Whitebeam's testbed based on this other question but i just can't get it to work. I'm trying to select the "pet" element that has a "description" child with a "Large dog!" value.

This is my best bet but it doesn't work and i don't get why:

I am dealing with the following dataset, which is keyed on Owner/Pet, and I am trying to query for those Owners that only have a dog:

Ideally, I would only get back the rows for Alex and Doug, however, the following SQL is just giving me back all the rows that have Dog: