-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(examples/cbdc): fix mismatch of Fabric identities in GET and POST requests #2802
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AndreAugusto11 I verified and it works. The caveat is still there that you have to manually refresh the page after having minted the tokens, but that's totally fine for a demo IMO.
FYI: I refactored the commit message and the PR title to not clutter the release notes showing this as a bug-fix in production code (it's an example so it won't make it to production)
LGTM
…equests The state keys were not being generated correctly for some reason It was working before without code changes so my best guess is that the Fabric ledger/SDK versions were changed and that's what tripped it up somehow. Fixes hyperledger-cacti#2739 [skip ci] Co-authored-by: Peter Somogyvari <[email protected]> Signed-off-by: André Augusto <[email protected]> Signed-off-by: Peter Somogyvari <[email protected]>
e1b8034
to
57b57ce
Compare
* What I believe has been an update to the Fabric SDK has lead the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping) * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint function was changed * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used in the frontend for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For the critical operations, access control is being performed by the chaincode by using the call in the begining of the relevant methods Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping) * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint function was changed * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping) * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint function was changed * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping) * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint function was changed * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in #2739 * An initial fix was deployed in #2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR #2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes #2914 Signed-off-by: André Augusto <[email protected]>
* What I believe has been an update to the Fabric SDK has led the application to break due to having the Fabric identities hardcoded (for the Fabric-Ethereum ID mapping). This was first noted in hyperledger-cacti#2739 * An initial fix was deployed in hyperledger-cacti#2802 but only the Mint was changed, which caused other functions to be breaking at the moment (e.g., Escrow) * This commit changes the crypto material files and reverts the workaround in PR hyperledger-cacti#2802 * The crypto material is only used for testing and to show information in the frontend (e.g., requesting the balance of a specific user based on the identity) * For critical operations, access control is being performed by the chaincode by using the call at the begining of the relevant methods Fixes hyperledger-cacti#2914 Signed-off-by: André Augusto <[email protected]>
docs(examples/cbdc): fix mismatch of Fabric identities in GET, POST requests
The state keys were not being generated correctly for some reason
It was working before without code changes so my best guess is that
the Fabric ledger/SDK versions were changed and that's what tripped it
up somehow.
Fixes #2739
[skip ci]
Co-authored-by: Peter Somogyvari [email protected]
Signed-off-by: André Augusto [email protected]
Signed-off-by: Peter Somogyvari [email protected]
cc: @petermetz @Anusha-Padmanabhan