Microsoft Azure Key Vault

Version 0.1.0 (OutSystems 11)
Published on 19 Feb by 
Coolprofs R&D
Coolprofs R&D
Created on 19 Feb

Microsoft Azure Key Vault

Documentation

To use it you need to have (of course) a key vault in Azure.

To be able to access it via this tool you need to have the following:

1. Register your application in Azure to be able to connect (https://porta;l.azure.com)

To register the connector application on open up your azure portal  at https://portal.azure.com. If you have an office 365 package you can login to azure using your office 365 admin credentials.  In the search bar at the top of the screen type in 'App Registration' and select.  You should see the below screen.

The following attributes you need to copy:

<<Client_Id>>

Specifies the Azure AD client id of the calling web service. To find the calling application's client ID, in the Azure portal, click Azure Active Directory, click App registrations, click the application. The client_id is the Application ID

<<Tenant_Id>>

Go to Portal.azure.com > Azure Active Directory > Properties. The directory ID it shows there is your tennant ID.

<<Client_Secret>>

Enter a key registered for the calling web service or daemon application in Azure AD. To create a key, in the Azure portal, click Azure Active Directory, click App registrations, click the application, click Settings, click Keys, and add a Key. This will be URL encoded when used


Don't forget to add the permission to the application to be able to access the Microsoft Azure Key Vault

 

2. The Actual Key Vault

Create/Use you KeyVault  in Azure.

<<VaultBaseURL>>

This is also needed, so grab this from the overview-tab and copy it the DNS-name. i.e. https::yourvaultname.vault.azure.net

In AccessPolicies tab make sure you add the in 1. generated application to have access to the Vault. At Least Get/List permissions


3. Create the Vault Mapping in Outsystems.

Simply call the Vault_Create action from MicrosoftAzureKeyVault

- VaultName name it wisely, can be different than teh actual vaultname, it's for outsystems internal use.

- VaultBaseURL, you should have it from step 2

- Client_Id, Client_Secret, Tenant_Id you should have gotten from step 1

- Resource_Id := https://vault.azure.net


4. Use the actions wisely.


The VaultName is the name you have provided in the Vault_Create.

The CertificateName, KeyName and SecretNames are the names you have given them in the KeyVault itself.


5. Final remarks

The component is under developments so it could be there are attributes not returned yet because of the enormous variations you could have.

Please let us know if you are missing certain attributes which you need.


Good luck and be safe out there!


Support Options
This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from Coolprofs R&D who created this component.
Dependencies
Microsoft Azure Key Vault has no dependencies.