Giter Club home page Giter Club logo

active-directory-verifiable-credentials-dotnet's Introduction

Microsoft Entra Verified ID Samples

This repo contains a set of Microsoft Entra Verified ID samples

Samples

Sample Description
1-asp-net-core-api-idtokenhint dotnet sample for using the VC Request Service API to issue and verify verifiable credentials with a credential contract which allows the VC Request API to pass in a payload for the Verifiable Credentials
2-asp-net-core-api-user-signin dotnet sample for a developer who wants to provide the signed-in users an option to get and present Verifiable credentials using the VC Request Service API. Note: This is different from 1-asp-net-core-api-idtokenhint sample as follows : User sign-in is a requirement to issue credentials since the credentials have claims (first name, last name) based on the signed-in user's idToken.'
3-asp-net-core-api-b2c dotnet sample for using the VC Request Service API to issue and verify verifiable credentials in a B2C policy
5-onboard-with-tap dotnet sample for onboarding new hire employees and guest users.

Microsoft provides a simple to use REST API to issue and verify verifiable credentials. You can use the programming language you prefer to the REST API. Instead of needing to understand the different protocols and encryption algorithms for Verifiable Credentials and DIDs you only need to understand how to format a JSON structure as parameter for the VC Request API.

API Overview

Issuance

The documentation for calling the issuance API is available here.

Verification

The documentation for calling the verification API is available here.

Setup

Before you can run any of these samples make sure your environment is setup correctly. You can follow the setup instructions here

Troubleshooting

If you are deploying this sample to Azure App Services, then you can view app logging information in the Log stream if you do the following:

  • Go to Development Tools, then Extensions
  • Select + Add and add ASP.NET Core Logging Integration extension
  • Go to Log stream and set Log level drop down filter to verbose

The Log stream console will now contain traces from the deployed.

Resources

For more information, see MSAL.NET's conceptual documentation:

active-directory-verifiable-credentials-dotnet's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

active-directory-verifiable-credentials-dotnet's Issues

IssuanceRequests is working but PresentationRequests gives an error

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [X] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I have created two different verifiable Ids and both of them are registered linked verified domains. (I have used two different Azure AD to register them)
Using one of the Verified ID credentials I am getting the credential (IssuanceRequests) while using another Verified ID credential I am trying to verify (PresentationRequest).
I am able to create the credential successfully and using the Microsoft Authenticator App, I have stored that credential in my mobile app. (I have used this repo code for that)
While I am trying to verify that's where I am getting an issue. I am able to generate the presentation request, I am getting the barcode correctly. However, when I use my Microsoft Authenticator App to scan that barcode it says " A Generic error has occurred on the server. No Authority" I have checked the payload and It has authority and that is the registered domain starts with did:web:....

Any log messages given by the failure

I am getting the log from Microsoft Authenticator App while I scan the presentation request is:
"Error Details: A generic error has occurred on the server."
After an upgrade to new version of Authenticator App I am getting new error. It says:
"Failed to send request. Unable to resolve host "beta.did.msidentity.com": No address associated with hostname."
During the troubleshooting activity, I found another version. It says
" A Generic error has occurred on the server. No Authority"

Expected/desired behavior

I was expecting that it will read my existing credentials stored in my App and suggest me which one to use and I select that and It will send that to verify.

OS and Version?

Windows 10

Versions

.Net Core 6

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Making request to https://beta.did.msidentity.com/ with result, "Unable to access KeyVault resource with given credentials."

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Download the sample (https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet.git)
Follow all instructions to setup, including creating the credentials, creating the application in AD, setting up the service principal, granting appropriate permissions as per instructions
Render site (using ngrok)
Generate qrCode with PIN successfully
Attempt to add credential to Authenticator wallet.
See error at Authenticator "Sorry, you can't go any further..."

Any log messages given by the failure

Error seen is:
Error Code: notFound
Error Details: VCNetworking.NetworkingError
code: 3

Timestamp: 2021-12-21T13:57:28.430Z
CorrelationId: Npp2XwaRRZmX5E6yYh+dew.1

Expected/desired behavior

Have authenticator view the credential that was issued

OS and Version?

Windows 10

Versions

Authenticator v 6.5.85

Mention any other details that might be useful

So, after some more reading the "not found" error I was getting is because the request identified by a given id is deleted after you request info about it the first time. Which explains this:

{"requestId":"a42cac57d63c7dff9f5e493a0a08a2ec","date":"Tue, 21 Dec 2021 14:48:41 GMT","mscv":"L1jOtLu4+sfiRusX.0","error":{"code":"client_request.token_id_not_found","message":"Requested '4f673355-d87b-45fa-ac70-942568310ce3' not found."}}

BUT. The real challenge seems to be this error:

{"requestId":"b488918157eed24d84d9c9a1dd48997d","date":"Wed, 22 Dec 2021 15:01:37 GMT","mscv":"8c4R3Z+pPmy2DwEG.1","error":{"code":"Forbidden","message":"Unable to access KeyVault resource with given credentials."}}

So, now, I'm wondering if this has something to do with KeyVault.

I checked my KeyVault and it seemed to contain entries for the VC Requester Service, the Issuer Service and my own service principal.

Here's more details from the log at that time:

2021-12-21 13:57:27.509 INFO VerifiableCredential 0 TID=1 141 (stopTrackCurrentMeasuredEvent()) DIDCardInfoPageViewed properties: ["CorrelationVector": "bYZXvIdhTJmK8d3MyYRhBg.0"]
2021-12-21 13:57:27.520 INFO VerifiableCredential 0 TID=1 93 (viewWillAppear()) DIDCardListViewed properties: ["CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.0", "Count": "0"]
2021-12-21 13:57:27.542 INFO VerifiableCredential 0 TID=1 55 (fire()) ["CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.1", "Message": "Correlation Vector for VCNetworking.FetchPresentationRequestOperation: Npp2XwaRRZmX5E6yYh+dew.1", "Function": "fire()", "File": "/Users/runner/work/1/s/PhoneFactor/VerifiableCredentialWallet/Submodules/VerifiableCredential-SDK-iOS/VCNetworking/VCNetworking/operations/NetworkOperation.swift", "Line": "55"]
2021-12-21 13:57:28.389 INFO VerifiableCredential 0 TID=1 39 (event(name:properties:measurements:)) DIDNetworkMetrics properties: ["CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.1", "eventName": "FetchPresentationRequestOperation", "CV_response": "", "code": "404", "CV_request": "Npp2XwaRRZmX5E6yYh+dew.1", "isSuccessful": "false"]
2021-12-21 13:57:28.394 ERRO VerifiableCredential 0 TID=1 44 (logNetworkingError(error:)) Error: nil Message: Networking Error: notFound(withBody: "{"requestId":"58858c6d0b7da3fd6b1b68f44dcc2afe","date":"Tue, 21 Dec 2021 13:57:28 GMT","mscv":"Npp2XwaRRZmX5E6yYh+dew.1.0","error":{"code":"client_request.token_id_not_found","message":"Requested '70933cb3-1e79-4f4d-b48c-082e5413f99c' not found."}}") Properties: ["File": "/Users/runner/work/1/s/PhoneFactor/VerifiableCredentialWallet/Submodules/VerifiableCredential-SDK-iOS/VCNetworking/VCNetworking/failureHandlers/SimpleFailureHandler.swift", "Line": "44", "ThrowableMessage": "", "Message": "Networking Error: notFound(withBody: "{\"requestId\":\"58858c6d0b7da3fd6b1b68f44dcc2afe\",\"date\":\"Tue, 21 Dec 2021 13:57:28 GMT\",\"mscv\":\"Npp2XwaRRZmX5E6yYh+dew.1.0\",\"error\":{\"code\":\"client_request.token_id_not_found\",\"message\":\"Requested \'70933cb3-1e79-4f4d-b48c-082e5413f99c\' not found.\"}}")", "CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.1", "Tag": "logNetworkingError(error:)", "Throwable": "nil"]
2021-12-21 13:57:28.406 ERRO VerifiableCredential 0 TID=1 79 (fetchFromUrl(url:)) Error: Optional(VCNetworking.NetworkingError.notFound(withBody: "{"requestId":"58858c6d0b7da3fd6b1b68f44dcc2afe","date":"Tue, 21 Dec 2021 13:57:28 GMT","mscv":"Npp2XwaRRZmX5E6yYh+dew.1.0","error":{"code":"client_request.token_id_not_found","message":"Requested '70933cb3-1e79-4f4d-b48c-082e5413f99c' not found."}}")) Message: Failed to get the presentation request Properties: ["Message": "Failed to get the presentation request", "CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.1", "Line": "79", "File": "/Users/runner/work/1/s/PhoneFactor/VerifiableCredentialWallet/VerifiableCredentialWallet/ViewModel/RequestProcessorViewModel.swift", "ThrowableMessage": "The operation couldn’t be completed. (VCNetworking.NetworkingError error 3.)", "Tag": "fetchFromUrl(url:)", "Throwable": "Optional(VCNetworking.NetworkingError.notFound(withBody: "{\"requestId\":\"58858c6d0b7da3fd6b1b68f44dcc2afe\",\"date\":\"Tue, 21 Dec 2021 13:57:28 GMT\",\"mscv\":\"Npp2XwaRRZmX5E6yYh+dew.1.0\",\"error\":{\"code\":\"client_request.token_id_not_found\",\"message\":\"Requested \'70933cb3-1e79-4f4d-b48c-082e5413f99c\' not found.\"}}"))"]
2021-12-21 13:57:28.413 INFO VerifiableCredential 0 TID=1 141 (stopTrackCurrentMeasuredEvent()) DIDPresentationRequest properties: ["Source": "QRScanner", "HasFailed": "true", "FirstTimeOnBoarding": "false", "CorrelationVector": "Npp2XwaRRZmX5E6yYh+dew.1"]
2021-12-21 13:57:28.415 VERB VerifiableCredential 0 TID=1 263 (navigateUsing(navigationBlock:)) navigateUsing: view had appeared previously CorrelationVector: Npp2XwaRRZmX5E6yYh+dew.1
2021-12-21 13:57:28.429 VERB VerifiableCredential 0 TID=1 90 (configure()) Showing error page with notFound details:Error: VCNetworking.NetworkingError code: 3 CorrelationVector: Npp2XwaRRZmX5E6yYh+dew.1


Thanks! We'll be in touch soon.

Cannot Issue Credential - "Something went wrong calling the API..Expiration Date cannot be used when Validity Interval is not allowed to be overridden."

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  1. Sign in with a B2C user
  2. Turn on dev tools in browser
  3. Click on Issue credential
  4. Get error in console "Something went wrong calling the API: {"requestId":"7afaf3c6e7914308c83ae68f3f8d5315","date":"Thu, 22 Feb 2024 04:11:05 GMT","mscv":"FfwA7VEvdQJ258Lg.3","error":{"code":"badRequest","message":"The request is invalid.","innererror":{"code":"badOrMissingField","message":"Expiration Date cannot be used when Validity Interval is not allowed to be overridden"}}}"

Any log messages given by the failure

Expected/desired behavior

present QR code for scanning followed by issuance of VC

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 11

Versions

22H2

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Needs Clarification - "You do not need to register an app or create a custom Verified ID credential schema."

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

n/a

Any log messages given by the failure

n/a

Expected/desired behavior

I am running the Azure B2C sample.
Clarification stating how the credential is accounted for if there is no need to create one any longer in the portal (or by other means) prior to running the samples. In previous samples (editions) display and rules files were provided which I have used as a guide when creating the credential in the portal that matches the credential type the sample expects. If this is no longer needed, will the latest version of this sample be creating this for us going forward? If that is the case, how will one fill in the manifest url when deploying the sample using the ARM template in the README (Deploy to Azure)? Also, the 'My Account' experience referenced in the README is only available of type Verified Employee, which does not align with a typical B2C use case

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Win 11

Versions

21H2

Mention any other details that might be useful


Thanks! We'll be in touch soon.

token_id_not_found or Requested authority could not be found

  • bug report

Minimal steps to reproduce

Download the sample (https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet.git)
Follow all instructions to setup, including creating the credentials, creating the application in AD, setting up the service principal, granting appropriate permissions as per instructions
Render site (using ngrok)
Generate qrCode with PIN successfully
Attempt to add credential to Authenticator wallet.
See error at Authenticator "Sorry, you can't go any further..."

Any log messages given by the failure

The first time I scan the code:
{"requestId":"44b2896dd8252de28853e35d6855a129","date":"Wed, 15 Jun 2022 09:44:57 GMT","mscv":"61u3wfBNQVCAe6jUETLECQ.1.0","error":{"code":"authorityNotFound","message":"Requested authority could not be found"}}

The following times I scan the code:
{"requestId":"e16b2d6ea088f2afea7dd5a00579027d","date":"Wed, 15 Jun 2022 09:27:31 GMT","mscv":"/+ALQqo0SOeLtRNswjz84g.1.0","error":{"code":"client_request.token_id_not_found","message":"Requested 'dd0d807a-7e23-4ef1-8295-3c16d049bff7' not found."}}

Expected/desired behavior

Have authenticator view the credential that was issued

OS and Version?

Windows 11

Versions

Authenticator v 6.5.85

Mention any other details that might be useful

com.microsoft.did.sdk.util.controlflow.NotFoundException: {"requestId":"cc21ab5fa1629e154aefb713d213da2d","date":"Wed, 15 Jun 2022 09:26:58 GMT","mscv":"tWF6o1FHRjSnwffBGJgKdQ.1.0","error":{"code":"authorityNotFound","message":"Requested authority could not be found"}}
at com.microsoft.did.sdk.datasource.network.BaseNetworkOperation.onFailure(BaseNetworkOperation.kt:66)
at com.microsoft.did.sdk.datasource.network.BaseNetworkOperation.fire$suspendImpl(BaseNetworkOperation.kt:44)
at com.microsoft.did.sdk.datasource.network.BaseNetworkOperation$fire$1.invokeSuspend(Unknown Source:11)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at androidx.lifecycle.DispatchQueue.drainQueue(DispatchQueue.kt:75)
at androidx.lifecycle.DispatchQueue.enqueue(DispatchQueue.kt:112)
at androidx.lifecycle.DispatchQueue.access$enqueue(DispatchQueue.kt:31)
at androidx.lifecycle.DispatchQueue$dispatchAndEnqueue$$inlined$with$lambda$1.run(DispatchQueue.kt:100)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7403)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:935)
[main]
2022-06-15 09:27:31,438 INFO/DID_SDK/: HttpError: 404 body: {"requestId":"e16b2d6ea088f2afea7dd5a00579027d","date":"Wed, 15 Jun 2022 09:27:31 GMT","mscv":"/+ALQqo0SOeLtRNswjz84g.1.0","error":{"code":"client_request.token_id_not_found","message":"Requested 'dd0d807a-7e23-4ef1-8295-3c16d049bff7' not found."}} cv: /+ALQqo0SOeLtRNswjz84g.1.0 [main]
2022-06-15 09:27:31,439 INFO/DID_SDK/: com.microsoft.did.sdk.util.controlflow.NotFoundException: {"requestId":"e16b2d6ea088f2afea7dd5a00579027d","date":"Wed, 15 Jun 2022 09:27:31 GMT","mscv":"/+ALQqo0SOeLtRNswjz84g.1.0","error":{"code":"client_request.token_id_not_found","message":"Requested 'dd0d807a-7e23-4ef1-8295-3c16d049bff7' not found."}}
at com.microsoft.did.sdk.datasource.network.BaseNetworkOperation.onFailure(BaseNetworkOperation.kt:66)
at com.microsoft.did.sdk.datasource.network.BaseNetworkOperation.fire$suspendImpl(BaseNetworkOperation.kt:44)
at com.microsoft.did.sdk.datasource.

Latest B2C ASPNetCoreVerifiableCredentialsB2C app will not build

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [X] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  1. git clone https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet.git
  2. Updated \3-asp-net-core-api-b2c\appsettings.json to known working configuration from prior version of this app
  3. dotnet restore
  4. dotnet build "AspNetCoreVerifiableCredentialsB2Cdotnet.csproj" -c Debug -o .\bin\Debug\netcoreapp3.1

Any log messages given by the failure

Build errors:

C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(69,17): error CS0117: 'VCPresentationRequest' does not contain a
 definition for 'includeReceipt' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(70,17): error CS0117: 'VCPresentationRequest' does not contain a
 definition for 'requestedCredentials' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(71,17): error CS0117: 'VCPresentationRequest' does not contain a
 definition for 'configuration' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(71,37): error CS0246: The type or namespace name 'Configuration'
 could not be found (are you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNet
CoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(72,38): error CS0246: The type or namespace name 'Validation' co
uld not be found (are you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCor
eVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(78,21): error CS1061: 'VCPresentationRequest' does not contain a
 definition for 'requestedCredentials' and no accessible extension method 'requestedCredentials' accepting a first argument of type 'VCPresentationRequest' could be found (are 
you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentials
B2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(135,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'type' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(136,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'manifest' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(137,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(144,29): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(154,29): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(160,41): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(167,37): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(174,41): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(194,52): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(236,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(239,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(243,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(264,35): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using direc 
tive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(267,34): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using direc 
tive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(269,38): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(270,53): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(272,68): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(273,68): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(277,79): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(282,34): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using direc 
tive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(324,39): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(324,80): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(325,38): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(333,71): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]

Build FAILED.

C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(69,17): error CS0117: 'VCPresentationRequest' does not contain a 
 definition for 'includeReceipt' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(70,17): error CS0117: 'VCPresentationRequest' does not contain a 
 definition for 'requestedCredentials' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]        
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(71,17): error CS0117: 'VCPresentationRequest' does not contain a 
 definition for 'configuration' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(71,37): error CS0246: The type or namespace name 'Configuration' 
 could not be found (are you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNet 
CoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(72,38): error CS0246: The type or namespace name 'Validation' co
uld not be found (are you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCor 
eVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(78,21): error CS1061: 'VCPresentationRequest' does not contain a 
 definition for 'requestedCredentials' and no accessible extension method 'requestedCredentials' accepting a first argument of type 'VCPresentationRequest' could be found (are  
you missing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentials 
B2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(135,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'type' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(136,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'manifest' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(137,21): error CS0117: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(144,29): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(154,29): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(160,41): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(167,37): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(174,41): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'claims' and no accessible extension method 'claims' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an a 
ssembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(194,52): error CS1061: 'VCIssuanceRequest' does not contain a defi 
nition for 'pin' and no accessible extension method 'pin' accepting a first argument of type 'VCIssuanceRequest' could be found (are you missing a using directive or an assembl 
y reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(236,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(239,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiIssuerController.cs(243,34): error CS1061: 'VCCallbackEvent' does not contain a defini 
tion for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using directi 
ve or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(264,35): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using direc 
tive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(267,34): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'requestStatus' and no accessible extension method 'requestStatus' accepting a first argument of type 'VCCallbackEvent' could be found (are you missing a using direc 
tive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.csproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(269,38): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(270,53): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(272,68): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(273,68): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(277,79): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(282,34): error CS1061: 'VCCallbackEvent' does not contain a defi 
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(324,39): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(324,80): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(325,38): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\ApiVerifierController.cs(333,71): error CS1061: 'VCCallbackEvent' does not contain a defi 
nition for 'verifiedCredentialsData' and no accessible extension method 'verifiedCredentialsData' accepting a first argument of type 'VCCallbackEvent' could be found (are you m 
issing a using directive or an assembly reference?) [C:\VerifiedIDB2C\active-directory-verifiable-credentials-dotnet\3-asp-net-core-api-b2c\AspNetCoreVerifiableCredentialsB2C.c 
sproj]
    0 Warning(s)
    30 Error(s)

Expected/desired behavior

App builds succesfully

OS and Version?

Windows 11

Versions

Mention any other details that might be useful


Issue seems to have started post this commit 324ba0d

Android deeplink not working

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Login on Android phone and wait for the timeout

Expected/desired behavior

Flow completes on phone using deeplink

The follow code causes the issue
´´´
window.location.href = respPresentationReq.url;
setTimeout(function () {
window.location.href = "https://play.google.com/store/apps/details?id=com.azure.authenticator";
}, 2000);
´´´

Fix: remove the setTimeout function. It would be nice to keep the timeout, but the 2s is not long enough as well.

´´´
window.location.href = respPresentationReq.url;
´´´

I could create a PR to remove this if you want

Greetings Damien

Works except it won't allow me to add the card in Authenticator

This issue is for a: (mark with an x)

- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Setup as per documentation
Run the sample app, launch the page via ngrok, try to GET CREDENTIAL
QR code appears and can be scanned. The code is accepted but the 'Add' button in Authenticator is greyed out

Any log messages given by the failure

Nope, stuck on "QR Code is scanned. Waiting for issuance..."

Expected/desired behavior

Add button is not greyed out > credential can be added to app

OS and Version?

Android 12

Versions

Authenticator v6.2207.4624

Mention any other details that might be useful

I have setup 1-asp-net-core-api-idtokenhint without issue and can Add credentials there just fine


Thanks! We'll be in touch soon.

Needs Clarification - "Note that Verified ID can not be onboarded in the B2C tenant as that is not supported." Yes but....

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

n/a

Any log messages given by the failure

n/a

Expected/desired behavior

When you create an Azure AD B2C resource, it comes with an Entra ID instance. You can see this when from the Home page you search for Entra ID (be sure your selected directory remains the Azure B2C directory). In This Entra ID instance, I can add a custom domain. Then I can go to Security => Verified ID and setup Verified ID with the Quick setup. It is not looking any different (so far) from using a regular Entra ID tenant. Is it then correct to say that we can use this B2C-associated Entra ID as a VC issuer and Verifier?

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Win 11

Versions

21H2

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Sample app is not generating QR Codes

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I have the sample app running via ngrok as per the MS guide, however the web page does not generate a QR code as mentioned in Step 5: https://docs.microsoft.com/en-gb/azure/active-directory/verifiable-credentials/verifiable-credentials-configure-verifier#run-and-test-the-sample-app

I see GET CREDENTIAL and VERIFY CREDENTIAL but when clicking on VERIFY it just takes me to a single button screen with no QR code. GET shows the same as well.

Any log messages given by the failure

None

Expected/desired behavior

QR code displayed on screen for scanning

OS and Version?

Windows 10 running Edge 100.0.1185.50

Versions

ver creds

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Unhandled ExceptionField 'exp' is required, but it was missing.

Reference: after setting up 2-asp-net-core-api-user-signin application as per document we are having issue while adding verifiable credential in MS authenticator app.

Here, after setting up required configuration it is generating QR code and once successfully scanned it asked for manual code.
Post this once I click "Add" in authenticator app it is throwing error instead of credential added success message.
Error message in authenticator app:
Unhandled ExceptionField 'exp' is required, but it was missing.

Please help and advise.

Is Attestation Verifiable Credentials Type repo demo available in c#?

I have tested successfully idtokenhint demo and I am trying unsucessfully attestation verifiable credentials type , similar to the Woodgrave Employee Onboarding Demo, is this code available in c#?

I can request the issuance of the VC but Authenticator doesn't request the ask the user to Present a verifiable credential in order to issue one, thus the issuance of the VC doesn't get authorized. In my case I need the Authenticator to request the VerifiedCredentialExpert VC first but I don't see how to trigger this on Authenticator, I tried this on issuance_request_config.json file, I also tried adding requestedCredentials to type VerifiedCredentialExpert as you see below to suggest to Authenticator to get this first, but didn't change the error behaviour:

  "includeQRCode": false,
  "callback": {
    //In this sample code we will overwrite the callback and use the HOSTNAME dynamicall
    //make sure you use ngrok or something like that when running on a local devbox. 
    //The MS AAD VC Request service needs to be able to reach the callback URI
    "url": "https://YOURPUBLICREACHABLEHOSTNAME/api/issuer/issuanceCallback",
    "state": "STATEWILLBESETINCODE",
    "headers": {
      "api-key": "OPTIONAL API-KEY for ISSUANCE CALLBACK API"
    }
  },
  //The Authority is the DID from your MS AAD Verifiable Credential service, you can copy this from the VC page in azure portal
  "authority": "did:ion: THIS IS YOUR DID FROM THE VC PAGE IN AZURE PORTAL WHICH IS SET IN THE SAMPLE BY COPYING THE VALUE FROM APPSETTINGS.JSON   ",
  "registration": {
    "clientName": "Verifiable Test Register Verifiable Credential"
  },
  //The type needs to be the same as defined in the rules json definitione. The manifest can be copied after the credential has been
  //created in the azure portal
  "type": "VerifiedTestRegistration",
  "manifest": "CREDENTIAL URL IN THIS SAMPLE WILL BE COPIED FROM APPSETTINGS.JSON",
  //Recommendation is to protect issuance payload with a PIN code. 
  //The pincode is set to a random value in code and will be displayed in the UI to the user
  "pin": {
    "value": "123456",
    "length": 4
  },
  //This is an example payload which will be used in the rules file of the credential.
  //The rules files maps information from the ID Token (hint) to the VC
  "claims": {
    "country_of_registry": "",
    "registration_number": "",
  },
  //You can request multiple verifiable credentials at once that's whty the requestCredentials is an array
  "requestedCredentials": [
    {
      "type": "VerifiedCredentialExpert",
      "purpose": "Required presentation of verifiable credentials expert to get Test Registration card.",
      //You can trust multiple issuers who might be issuing the same credential type (for example certifications or diplomas)
      //You need to specify at least 1 trusted issuer DID, for this sample code we copy the IssuerAuthority from appsettings to the request
      //"acceptedIssuers": [ "did:ion: copied from your VC portal in this sample the code copies it from APPSETTINGS.JSON" ]
      "acceptedIssuers": [ "theaccepetedidissuer" ]
    }

  ]
}
 
These are the display and rules:

`Display definition
    {
      "locale": "en-US",
      "card": {
        "title": "Test Verified Credential",
        "issuedBy": "TheIssuer",
        "backgroundColor": "#000000",
        "textColor": "#ffffff",
        "logo": {
          "uri": "https://domain.com/image.png",
          "description": "Test  Verified Credential"
        },
        "description": "Use this card to verify."
      },
      "consent": {
        "title": "Do you want to get your Test Verified Credential?",
        "instructions": "Sign in with your Verified Credential Expert Card to get your card."
      },
      "claims": [
        {
          "claim": "$.vc.country_of_registry",
          "label": "Country of Registry",
          "type": "String"
        },
        {
          "claim": "$.vc.registration_number",
          "label": "Registration Number",
          "type": "String"
        }
      ]
    }

    Rules definition
    {
    "attestations": {
      "presentations": [
        {
          "mapping": [
            {
              "outputClaim": "firstName",
              "required": true,
              "inputClaim": "$.vc.credentialSubject.given_name",
              "indexed": false
            },
            {
              "outputClaim": "lastName",
              "required": true,
              "inputClaim": "$.vc.credentialSubject.family_name",
              "indexed": false
            }
          ],
          "required": true,
          "credentialType": "VerifiedCredentialExpert",
          "contracts": [
            "https://verifiedid.did.msidentity.com/v1.0/tenants/id/verifiableCredentials/contracts/abcd/manifest"
          ],
          "trustedIssuers": [
            "did:ion:thedid"
          ]
        }
      ],
      "idTokenHints": [
        {
          "mapping": [
            {
              "outputClaim": "countryOfRegistry",
              "required": true,
              "inputClaim": "$.country_of_registry",
              "indexed": false
            },
            {
              "outputClaim": "registrationNumber",
              "required": true,
              "inputClaim": "$.registration_number",
              "indexed": true
            }
          ],
          "required": true
        }
      ]
    },
    "validityInterval": 2592000,
    "vc": {
      "type": [
        "VerifiedTestRegistration"
      ]
    }
  }`

I am testing on iphone12 pro latest iOS version installed.

Thank you for your help, Sergio


### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
>

### Any log messages given by the failure
>

### Expected/desired behavior
>

### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

### Versions
>

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Close Microsoft Authenticator app (Android) and return to browser

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

On an Android phone, when I complete the presentation flow using the deeplink, the Microsoft Authenticator app does not close and the user is NOT returned to the browser.

How can I close the Microsoft Authenticator app and return the user to the browser?

Code:

´´´
window.location.href = respPresentationReq.url;
´´´

Greetings Damien

Doc bug: NGROK port is incorrect

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/README.md#running-the-sample

says to run ngrok under port 3000 which should be port 5000

When you run it and connect ngrok will error out:

**The connection to https://43af-67-160-105-6.ngrok.io/ was successfully tunneled to your ngrok client, but the client failed to establish a connection to the local address localhost:3000.

Make sure that a web service is running on localhost:3000 and that it is a valid address.**

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Managed Identity not working - "Provided access token contains no roles"

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  1. Set managed identity to true when deploying the web app
  2. Run provided powershell to grant managed identity application permissions to the verifiable credentials service
  3. Attempt to issue a credential
  4. error seen in dev tools "Provided access token contains no roles"

I had to switch to using an app registration with a credential. When I did that, error "Provided access token contains no roles" went away. But got another - "Something went wrong calling the API..Expiration Date cannot be used when Validity Interval is not allowed to be overridden." Opened a different issue for that here - #64.

Note that I even tried to reapply the permissions by running the powershell again but got an error that mentioned the permissions are already applied. But ran Get-AzureADServiceAppRoleAssignment on the managed identity and it returned nothing. Might try an MG-Graph cmdlet later.

Any log messages given by the failure

"Provided access token contains no roles"

Expected/desired behavior

Successful call to the VC request service

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Win 11

Versions

22H2

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Second Sample - PresentationCallback of VC fails

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Just configure the second sample and try to present the VC that was issued. You'll get an error on the Authenticator app and diagnosis information on the Authenticator app doesn't give you a hint about the issue. I debugged the sample and it looks like the line on 224 (on VerifierController.cs) is causing the issue. e.g. //payload = presentationResponse["issuers"].ToString(),

According the ngrok, the callback URL receives the following data

payload

which doesn't have a key with "issuers", so I commented out this line. Instead, one can also use
payload = presentationResponse["verifiedCredentialsData"][0]["issuer"].

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Subproject nº3 - Error claims exchange 'REST-VC-GetAuthResult'

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Following the project guide number 3 and having deployed the “B2C Custom Policy Starter Pack - LocalAccounts” policies, I have deployed the web app in Azure correctly: I can do the login, Issue Credential and Verifiy Credential correctly.

Any log messages given by the failure

When I want to login using the QR and I present a valid card, I get this error:
The claims exchange 'REST-VC-GetAuthResult' specified in step '2' returned HTTP error response with Code 'BadRequest' and Reason 'Bad Request'. I think it is a issue with the “TrustFrameworkExtensionsVC.xml” policy.

Also, when you Sign Out, it redirects to a blank page instead of the Home page.

Expected/desired behavior

Login to the web app with the QR of the VC.

OS and Version?

I'm running this in the Web app, in Azure.

Versions

DotNet v6

Mention any other details that might be useful


Thanks! We'll be in touch soon.

no selfie being added to the Verified Credential in Authenticator

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Scan the Selfie QRCode and after taken selfie and clicked on "Use photo".

Any log messages given by the failure

No error logs being shown. Just that selfie is taken message.

Expected/desired behavior

The Selfie/photo added to the Verifiable credential card in Authenticator.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

The selfie/photo


Thanks! We'll be in touch soon.

Request authority cloud not be found

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

As testing the Verifiable credentials (Preview) I created an organization with an verified domain.

image

Also I created a credential with an ManifestURL. As described in the documentation I filled the right values in the appsettings file.
When I run the App and want to issue a credential I get an QR Code.

image

But when I scan the QR - Code I get an error message / 404. What am I doing wrong?

image

image

image

Any log messages given by the failure

/

Expected/desired behavior

OS and Version?

Windows 10 - .NET 5
Authenticator - 6.5.98

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Subproject nº3 - error custom B2C XML upload Azure

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I am following the guide provided in this GitHub (https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/3-asp-net-core-api-b2c/B2C/README.md#setup). I have configured the B2C Tenant, configured and uploaded to the B2C the "B2C Custom Policy Starter Pack - LocalAccounts"; also the REST API, the web application...

The problem is that I have configured the B2C Custom Policies, and I have uploaded them to the "Identity Experience Framework" section of Azure, but the XML of "SignUpOrSignInVCQ.xml" and "SignUpVCOrSignin.xml", I get an error.

Question: the 6 custom policies (https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/tree/main/3-asp-net-core-api-b2c/B2C/policies), do they have to be uploaded all 6 to Azure, to work properly?

Any log messages given by the failure

SignUpOrSignInVCQ.xml

Validation failed: 5 validation error(s) found in policy "B2C_1A_VC_SUSIQ" of tenant "xxxxxx.onmicrosoft.com".User journey 'SignUpOrSignIn' in policy 'B2C_1A_VC_susiq' of tenant 'xxxxxx.onmicrosoft.com' has 2 sendClaims steps. Please specify a DefaultCpimIssuerTechnicalProfileReferenceId attribute set to the default issuer technical profile reference id.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.
User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.User journey 'SignUpOrSignIn' in policy 'B2C_1A_VC_susiq' of tenant 'xxxxxx.onmicrosoft.com' has 2 sendClaims steps. Please specify a DefaultCpimIssuerTechnicalProfileReferenceId attribute set to the default issuer technical profile reference id.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susiq" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.

SignUpVCOrSignin.xml

Validation failed: 5 validation error(s) found in policy "B2C_1A_VC_SUSI_ISSUEVC" of tenant "xxxxxx.onmicrosoft.com".User journey 'SignUpOrSignIn' in policy 'B2C_1A_VC_susi_issuevc' of tenant 'xxxxxx.onmicrosoft.com' has 2 sendClaims steps. Please specify a DefaultCpimIssuerTechnicalProfileReferenceId attribute set to the default issuer technical profile reference id.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.User journey 'SignUpOrSignIn' in policy 'B2C_1A_VC_susi_issuevc' of tenant 'xxxxxx.onmicrosoft.com' has 2 sendClaims steps. Please specify a DefaultCpimIssuerTechnicalProfileReferenceId attribute set to the default issuer technical profile reference id.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "5" but it was not found.User Journey "SignUpOrSignIn" in policy "B2C_1A_VC_susi_issuevc" of tenant "xxxxxx.onmicrosoft.com" was expected to have step with order "6" but it was not found.

Expected/desired behavior

Upload the 6 custom policies to the "Identity Experience Framework" section of Azure, without errors.

OS and Version?

I'm running this in the Web app, in Azure.

Versions

DotNet v6

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.