authority | https : //github.com/cxjava/authority.git

So the seed approach is a PDA, which is actually what #associated was using underneath the hood

You will need a function that initializes the seed with the below init and payer trait. payer should also be the same user who is actually paying the for transaction.

Please note that #[instruction(bump: u8] is matching the signature of the function here, hence you will need to pass in the bump in the signature as the first argument.

My problem is that I can't seem to parse the NAME in the answer section. It seems to start with a pointer which makes no sense.

I probably know at lot less about this than you but am wondering why you say that? firstByte is telling you there's a pointer and the following value (0x0c) shows you the offset of the name for compression purposes (if I've got that right). None of the other bits in the same byte as firstByte is set so that can be ignored from the point of view of the offset value

how do i access my connected services, without actually storing the credentials of accessing the azure key vault?

• Use Azure AD Managed Service Identity to access Key Vault from all environments without storing any credentials in the app.
• Managed Identity provides Azure services with an automatically managed identity in Azure Active Directory .
• It helps to authenticate to any service that supports AAD authentication without maintaining credentials in your code.
• It is a great feature from a security perspective because credentials are not accessible to you.
• Managed identities can be used without any additional cost.

Refer steps to read a secret stored in an Azure Key Vault instance and Use a managed identity to connect Key Vault to an Azure web app in .NET

how do i manage two key vaults within one solution (one for dev env and one for prod env)?

Refer managing key vaults in Development environment , Production environment and Production and Development environments

Please refer this for more information

Microsoft.Data.SqlClient 4.0 is using ENCRYPT=True by default. Either you put a certificate on the server (not a self signed one) or you put

TrustServerCertificate=Yes;

on the connection string.

Finally I was able to resolve the issue as follows:

I've found the following documentation:

Setting up certificates for Azure CLI on Azure Stack Development Kit

The basic idea is to find the python installation used for Azure CLI and update the related certificate file.

In my case the Azure CLI was installed with python on the following location:

C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe

And using the command, that was suggested, returned as follows:

Picking up on the comment by @salparadise, the following worked for me:

I've created a simplified setup starting from your code with support for both OAuth2 and Basic Auth.

/tenant2/** will start a basic authentication. /** (everything else) triggers an OAuth2 Authorization Code authentication.

The key to achieve this is to have one @Configuration class per authentication type.

Let's start with the controllers:

Tenant1HomeController

In your example 1domain is a TLD (top level domain). If to look at this spec it states:

A TLD label MUST be at least two characters long and MAY be as long as 63 characters - not counting any leading or trailing periods (.). It MUST consist of only ASCII characters from the groups "letters" (A-Z), "digits" (0-9) and "hyphen" (-), and it MUST start with an ASCII "letter", and it MUST NOT end with a "hyphen". Upper and lower case MAY be mixed at random, since DNS lookups are case-insensitive.

You are advised to use the following method to validate the token.