OpenFlag | source feature flagging , A/B | Access Management library

This issue occurs on MacOS using VSCode to debug an individual test (instead of the entire suite). When I try to debug this test with vscode, I get the following output:

I am trying to run my xUnit tests within VSCode using the Run CodeLens .

I am using VSCode 1.65.0 with .Net 6 (6.0.200) on a 2019 MacBook Pro (Intel) with the v1.24.1 of the C# VSCode extension.

I have run it using the dotnet test command, the .NET Core Test Explore Plugin and VS2022, and these work as expected.

This is the output log I get

I get an error when trying to sign data with .NET Core using CMS with certificate

I have small lambda function which donwload files from s3 buckets, create zip of it and upload on S3 bucket again.

My lambda function use .net core3.1.

I can write text file but not create zip file.

Zip File Code in C# (as it deployed in linux system, hence I tried to create zip file in Tmp direcotry)

I have below 2 methods,

GetCaCertificate method reads the PFX certificate with has private key included.

AddCertToStore method add the certificate to the certificate store, here I want to add the certificate in the certificate store with-out Private key, how we can avoid it?

I read some posts (that don't exist anymore) and came up with the following code that generates a PFX certificate. It works fine to the part of creating this self-signed certificate.

I'm trying to expand this to crate a self-signed certificate and from that one, create it's "childs". I tryed many things but none of then actually export the certificate with it's chain as result.

The current code get's to a point of exporting a PFX with a containing CA and importing it would include both certificates, but not associate then with each other.

It's kind of a long code, but the action should work on the last "Create" funcion of it.

I'm having trouble with a very simple C# program that opens two SQLite files and reads the contents.

Program works fine (button1) when database file is on local machine, but I cannot get it to work (button2) when the file is on another LAN PC (both running Windows 10).

I'm using Visual Studio 2019 to write this Windows Application using .Net Framework 4.7.2

My code is simple. It's two buttons that do the same thing, but one for a local file and the other for a file on the LAN PC. Here's my code:

I'm working on a simple tool for a test environment where I have to set up a few dozen sites through C# code. Thus I have a list of (sub)domain names (and other properties) in an array and I run through it to create the sites with their bindings. This works fine, except for the HTTPS bindings where I need to bind the proper SSL certificates from the store. For whatever reason, all sites end up with the same certificate.
The code is relatively straightforward. I first open the certificate store like this:

I am attempting to set up a Magic link like system using Azure B2C. Using the following samples: Primary:
https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-magic-link

For sing B2C to generate the metadata endpoints: https://github.com/azure-ad-b2c/samples/tree/master/policies/invite#using-b2c-to-generate-the-metadata-endpoints

As a note I believe I had it working at one point but after a clean up I have been getting the error:

The provided id_token_hint parameter failed signature validation. Please provide another token and try again.

The steps I took to set up is as follows:

1. Create a cert via powershell and get thumbprint to use in local code
2. Use certmng via MMC to export cert
   • All Task / Export / Next / Yes, Export the private key
   • Personal Information Exchange - PKCS (Include all cert in cert path)(Enable cert privacy)
3. Security (Password) Randomly Generated Pass 25 character password.
4. Name: id_token_hint_cert.pfx
5. Browse Azure / B2C / Identity Experience Framework / Policy keys
   • Add / Option: Upload / Name: IdTokenHintCert / File Upload id_token_hint_cert.pfx / Password: Password from setup 3

This is where I have tried 2 different set ups. The first was to setup a set of custom policies so that I could update the following claims provider to have issuer_secret set to B2C_1A_IdTokenHintCert