There are several ways to do this. You could use the “Paragraph” method, JS / CSS or add extra text to the claims “DisplayName”. But you can also add the text as input fields: <InputClaims> <InputClaim ClaimTypeReferenceId="label_text" DefaultValue="Some wording" AlwaysUseDefaultValue="true"/> </InputClaims> <OutputClaims> <OutputClaim ClaimTypeReferenceId="label_text" /> </OutputClaims> All good!

From the docs: “DIDs are user-generated, self-owned, globally unique identifiers rooted in decentralized systems like ION. They possess unique characteristics, like greater assurance of immutability, censorship resistance, and tamper evasiveness. These attributes are critical for any ID system intended to provide self-ownership and user control. Microsoft’s verifiable credential solution uses…

There’s a good overview here. Imagine Woodgrove is a trusted site that issues credentials. My site offers a discount to all Woodgrove employees. The question is how do I know what “metadata” to use (Woodgrove DID’s etc.) to accomplish this. This is what the verified ID network is used for. …

The Github sample is here. I used “OPTION 2 (Manually importing the postman collection and environment JSON files)”. I used the Postman Scratchpad to do this. I also have the .NET sample working so I could get most of the settings from appsettings.json.

I often have the case where I’ve written a custom policy, but the other pieces required to deploy it, e.g. REST API, databases etc., aren’t ready, but I still want to test the logic. I create a unit test Technical Policy that the policy calls, and I add all the flags that would derive from the API etc., in there e.g. <OutputClaim ClaimTypeReferenceId="extension_Flag1" DefaultValue="True" AlwaysUseDefaultValue="true" />

First, read part 1. Part 1 is a website that issues and verifies VC. Part 2 is a B2C custom policy that uses the API in the website to issue and verify a VC from B2C. The custom policies and HTML are here. We will use the SignupOrSigninVCQ policy. There…

If you haven’t read the first article, have a read here. Setup the basic VC stuff as per that article. The Github sample is here. There are three .NET samples there. The above link refers to the first sample.

CIAM External ID was announced at Build and is currently in public preview. CIAM (Customer IAM) is the successor to Azure AD B2C. And, of course, I then got a million questions about the future of B2C, so I decided to write this post. Note that the product has just…

I’ve been playing around with the samples for Verified ID and one of the key points is getting the Azure AD configuration correct. The docs. for the configuration are here. There are some tools to help you. ION Explorer The first is the ION Explorer.