EntraIDVerifiedIDmDLAspNetCore

2025-12-10 0 266

ASP.NET Core Issue and Verify Verifiable Credentials using Microsoft Entra Verified ID

Blogs

  • Getting started with Self Sovereign Identity SSI
  • Challenges to Self Sovereign Identity
  • Create and issue verifiable credentials in ASP.NET Core using Azure AD

History

  • 2024-12-15 .NET 9, Updated packages
  • 2023-07-29 Updated packages
  • 2023-06-24 Updated VC, using mDL based driving license
  • 2023-06-23 Update subject model, based on https://git*hu*b.*com/w3c-ccg/vdl-vocab/blob/main/context/v1.jsonld
  • 2023-06-18 Updated packages
  • 2023-04-28 Updated packages
  • 2023-03-05 Fixed new VC payloads, fixed cache, recreated all VCs, added github actions for Azure deployment
  • 2023-03-03 Updated to .NET 7, Update AAD VC service with all the breaking changes
  • 2022-03-18 Updated code
  • 2021-11-12 Updated to .NET 6 release

User secrets and issuer/verify configuration

Select the correct endpoint depending to the business of the application.

{
  \"CredentialSettings\": {
    \"Endpoint\": \"https://verifiedid.**di*d.msidentity.com/v1.0/verifiableCredentials/createPresentationRequest\",
    //  \"Endpoint\": \"https://verifiedid.di*d.m**sidentity.com/v1.0/verifiableCredentials/createIssuanceRequest\",
    \"VCServiceScope\": \"bbb94529-53a3-4be5-a069-7eaf2712b826/.default\",
    \"Instance\": \"https://login.*microsofto*nl*ine.com/{0}\",
    \"TenantId\": \"YOURTENANTID\",
    \"ClientId\": \"APPLICATION CLIENT ID\",
    \"VcApiCallbackApiKey\": \"SECRET\",
    \"Authority\": \"YOUR authority\",
    \"ClientSecret\": \"[client secret or instead use the prefered certificate in the next entry]\",
    // \"CertificateName\": \"[Or instead of client secret: Enter here the name of a certificate (from the user cert store) as registered with your application]\",
    \"IssuerAuthority\": \"YOUR VC SERVICE DID\",
    \"VerifierAuthority\": \"YOUR VC SERVICE DID\",
    \"CredentialManifest\":  \"THE CREDENTIAL URL FROM THE VC PORTAL\"
  }
}

Iso18013 Drivers License (mDL) scheme

I would like to base this on a standard scheme, but could not find any.

Found 2 drafts:

https://git*hu*b.*com/w3c-ccg/vdl-vocab/blob/main/context/v1.jsonld

https://w3c-ccg.g**i*thub.io/vdl-vocab/

Local debugging, required for callback

ngrok http https://l*ocalh*ost:*5001

Feedback in issuer app

When running the issuer application, ngrok is used if you would like to receive feedback from the VC issuing through the callback. This requires a public IP. The IP needs to be added to the Azure App Registration as a redirect URL to authenticate. ngrok is only used for development.

CredentialsClaims

The CredentialsClaims classes in both the issuer and the verifier are used to add the specific claims to the definition of the Azure VC credential.

The classes must match the definitions. By changing these classes and the rules fields, different Azure verifiable credentials can be used.

GetIssuanceRequestPayloadAsync

This method defines the specifics of the issue request payload. This would need to be changed, if you required no pin verification or other flows. See the Azure AD VC docs for more info.

Microsoft sample APP

sample

Database

Add-Migration \"init\"

Update-Database

Links

https://docs.*mi*cr*osoft.com/en-us/azure/active-directory/verifiable-credentials/

https://docs.*mi*cr*osoft.com/en-us/azure/active-directory/verifiable-credentials/get-started-request-api

https://gi**t*hub.com/Azure-Samples/active-directory-verifiable-credentials-dotnet

https://www.m*icro**soft.com/de-ch/security/business/identity-access-management/decentralized-identity-blockchain

https://didproject.a*zu*rewebsi*tes.net/docs/issuer-setup.html

https://didproject.az**urewebsit*es.net/docs/credential-design.html

https://githu**b.c*om/Azure-Samples/active-directory-verifiable-credentials

https://*id*e*ntity.foundation/

https://www.*w**3.org/TR/vc-data-model/

https://daniel-krzyczkowski.***github.io/Azure-AD-Verifiable-Credentials-Intro/

https://do*tnet*th*oughts.net/using-node-services-in-aspnet-core/

https://*id*e*ntity.foundation/ion/explorer

https://www.n*pmj**s.com/package/ngrok

https://gith*ub*.c*om/microsoft/VerifiableCredentials-Verification-SDK-Typescript

https://*id*e*ntity.foundation/ion/explorer

https://www.n*pmj**s.com/package/ngrok

https://gith*ub*.c*om/microsoft/VerifiableCredentials-Verification-SDK-Typescript

下载源码

通过命令行克隆项目:

git clone https://github.com/swiss-ssi-group/EntraIDVerifiedIDmDLAspNetCore.git

收藏 (0) 打赏

感谢您的支持,我会继续努力的!

打开微信/支付宝扫一扫,即可进行扫码打赏哦,分享从这里开始,精彩与您同在
点赞 (0)

申明:本文由第三方发布,内容仅代表作者观点,与本网站无关。对本文以及其中全部或者部分内容的真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。本网发布或转载文章出于传递更多信息之目的,并不意味着赞同其观点或证实其描述,也不代表本网对其真实性负责。

左子网 编程相关 EntraIDVerifiedIDmDLAspNetCore https://www.zuozi.net/33358.html

常见问题
  • 1、自动:拍下后,点击(下载)链接即可下载;2、手动:拍下后,联系卖家发放即可或者联系官方找开发者发货。
查看详情
  • 1、源码默认交易周期:手动发货商品为1-3天,并且用户付款金额将会进入平台担保直到交易完成或者3-7天即可发放,如遇纠纷无限期延长收款金额直至纠纷解决或者退款!;
查看详情
  • 1、描述:源码描述(含标题)与实际源码不一致的(例:货不对板); 2、演示:有演示站时,与实际源码小于95%一致的(但描述中有”不保证完全一样、有变化的可能性”类似显著声明的除外); 3、发货:不发货可无理由退款; 4、安装:免费提供安装服务的源码但卖家不履行的; 5、收费:价格虚标,额外收取其他费用的(但描述中有显著声明或双方交易前有商定的除外); 6、其他:如质量方面的硬性常规问题BUG等。 注:经核实符合上述任一,均支持退款,但卖家予以积极解决问题则除外。
查看详情
  • 1、左子会对双方交易的过程及交易商品的快照进行永久存档,以确保交易的真实、有效、安全! 2、左子无法对如“永久包更新”、“永久技术支持”等类似交易之后的商家承诺做担保,请买家自行鉴别; 3、在源码同时有网站演示与图片演示,且站演与图演不一致时,默认按图演作为纠纷评判依据(特别声明或有商定除外); 4、在没有”无任何正当退款依据”的前提下,商品写有”一旦售出,概不支持退款”等类似的声明,视为无效声明; 5、在未拍下前,双方在QQ上所商定的交易内容,亦可成为纠纷评判依据(商定与描述冲突时,商定为准); 6、因聊天记录可作为纠纷评判依据,故双方联系时,只与对方在左子上所留的QQ、手机号沟通,以防对方不承认自我承诺。 7、虽然交易产生纠纷的几率很小,但一定要保留如聊天记录、手机短信等这样的重要信息,以防产生纠纷时便于左子介入快速处理。
查看详情

相关文章

猜你喜欢
发表评论
暂无评论
官方客服团队

为您解决烦忧 - 24小时在线 专业服务