Contract Negotiation Failed with BPN Outside Seed Data - Unable to Obtain the Credentials #202
Comments
saudkhan116
changed the title
|
Hi @saudkhan116 , Could you share the Postman collection that you are using to achieve this result? |
Hi @CDiezRodriguez, The APIs that I use are the same as described in EDC Walkthrough APIs here. |
|
Hi @saudkhan116, I tried running the queries related to EDR up to this point (the picture below), and everything seems to be okay. Maybe you can do a PR updating the Postman collection with the new queries you want to execute.
|
Hi @CDiezRodriguez, yes, this works fine because the BPNs you used is already a part of seeding data. Hence, everything is already configured during the startup process. Please follow the Steps to Reproduce the issue (above), and use the BPN |
|
Hi @saudkhan116 , I managed to set the consumer with the new BPNLARN000000011 and got the same error as you. You have two options to fix this:
|
Hi @CDiezRodriguez, I want to go through the company onboarding process, which is done against the BPN The second option, we dont want to hard code the values, especially in a case where central services and EDCs are hosted in two different locations. Simply, we need to test the new BPNs (recieving from company onboarding) without having a part of any seeding process. |
|
Hi @saudkhan116, I can't see the creation of the wallet for BPNLARN000000011. If it has been created, it should appear in the log of the SSI-DIM-WALLET-STUB, similar to the following line: Request to setup dim received for company name -> Eclipse Tractus-x Operating Company, bpn ->BPNL00000003CRHK waiting for 60 sec |
Ok. Let me test this again, and update you. |
|
@saudkhan116 is testing |
and others
Problem Statement:
I have a new BPN number BPNLARN000000011 which was obtained from the company registered into the Portal. I need to run the EDC against this BPN number, and perform e2e data exchange journey using EDC walkthrough APIs. During the company onboarding process, it was ensured that the BPN got registered by the Identity Wallet and all necessary steps have been taken from the application_checkilist to make the registration successful. The data offers can be seen in EDC contract catalog, however the EDR Token is not getting generated and EDC provider logs the exception and reports the error message "Unable to Obtain the Credentials"
The default BPNs, used in the seed data work fine in the data exchange. The intention is to utilize a new BPN without modifying anything from the chart values.yaml. Some screenshots are attached, that might help to further diagnose the issue.
Request EDR Token API
Actual Behavior
The empty Response
Expected Behavior
There should be the contract agreement details once the contract is negotiated between data consumer and data provider.
Steps to Reproduce
BPNLARN000000011BPNLARN000000011as shown in the above values.yaml file snippetEDC Configuration
In the EDC configuration, only BPN is changed. The rest of the settings remain same
values.yaml
Did Resolution in the wallet below:
Url: {{walletUrl}}/BPNLARN000000011/did.json
EDC Contract Catalog
Logs
EDC Consumer Logs:
EDC Provider Logs:
SSI DIM Wallet stub Logs:
The logs from the ssi-dim-wallet report no errors
I expected that the error came from not mapping service account against the BPN in Keycloak. Therefore, I created new client in Keycloak
satest20and grant it theIdentity Wallet Managementrole.The text was updated successfully, but these errors were encountered: