Skip to content

Latest commit

 

History

History
54 lines (37 loc) · 2.3 KB

README.md

File metadata and controls

54 lines (37 loc) · 2.3 KB
Raw

Prototype DID Enterprise Agent

Steps to deploy via Azure portal

  1. Click the Deploy to Azure button below.
  2. Fill out the details in the Azure portal with your own values.
  3. Click Purchase, and wait for deployment to complete! You can view the status of your deployment by navigating to your resource group and clicking on Deployments.

Steps to deploy using Azure CLI

  1. Clone the repo
  2. Change the values in azuredeploy.parameters.json to your own values.
  3. Login to the Azure CLI:
az login
  1. Choose a resource group in which to create your enterprise agent. If you don't have one, the following command creates a new resource group:
az group create --location eastus --name my-new-resource-group
  1. Run the command below to create the enterprise agent and all associated resources in the resource group:
az group deployment create --resource-group my-new-resouce-group --template-file azuredeploy.json --parameters '@azuredeploy.parameters.json'

Using the enterprise agent

The enterprise agent currently only has one function. Simply hit the home page of your web service to have a hard-coded verifiable credential returned from the enterprise agent. The URL for your web service will be something like:

https://my-enterprise-agent.azurewebsites.net

Where my-enterprise-agent is the name of the web app you provided during deployment.

Troubleshooting

  • Occasionally, you may get an error during deployment of authorization rules that says "Principal does not exist in directory ." You can simply retry the deployment, usually the error goes away.
  • The name of your storage account must be between 3-24 characters, should only contain lowercase letters and numbers, and must by globally unique.
  • The name of your web app must be globally unique.