IdentityService | Manages user registration confirmation credentials | Authentication library

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

You have to send the query and body as variables in post request like shown here

After our discussion in the above comments section, it appears that your states have been issued using Whitelist zone constraint.

Also looking at the code it is clear that you have not explicitly added Whitelist Zone constraints for your states. Then there remain two more possibilities by which states are issued using Whitelist Zone constraint.

One is you are using some Corda version before 4 or you have included the necessary configs to include white list zone constraints in network bootstrapper as specified here. You have two options - either start from scratch and make sure you use Corda 4.

If you cannot start from scratch follow this path to first migrate the whitelist zone constraints to signature constraints, before running your UpdateLoadFlow. You can refer to this blog which talks about constraint migration.

Based on your error message it seems that you are trying to resolve JwtService in your Newproject.Infrastructure.Identity.IdentityService but you have only interface registration:

import * as Authentication imports the module's module namespace object, which has properties for each of the module's exports; it's not constructible.

You haven't shown any export of AuthenticationServices, so it's hard to tell you how to import it. If you exported it as a named export (generally preferred), like this:

Your title says you are using Java 9. With Activiti 6 you will have to use JDK 1.8 (Java 8).

Rather than redefining QService in AppModule's providers, QModule should have QService in both providers and exports. This will allow any module that imports: [QModule] to make use of the exports of QModule without needing to redefine the provider.

As a side note, every time you add a provider to the providers array of a module, that will be a new instance of said provider. In this case, there's two instances, and the AppModule wants access to everything QService needs. This is why you should use exports instead.

PromiseResult is an object that includes .promise as a function. Then, when you want to mock a function to return a PromiseResult, the mock data should be an object like PromiseResult.

In your case, mockData should be:

This was an issue with mixing IdentityServer and ASP.net identity.

By removing Microsoft.AspNetCore.ApiAuthorization.IdentityServer and the use of base class from ApiAuthorizationDbContext back to IdentityDbContext resolved this.