business-partner-agent GitHub

PR #401	added mycila license plugin, enabled check goal, and reformatted all …
	…headers Signed-off-by: Philipp Etschel <philipp.etschel@ch.bosch.com>

Created At 2021-04-27 11:24:10 +0000 UTC

PR #400	#367 Manual connection request - backend part

Created At 2021-04-27 10:42:59 +0000 UTC

PR #399

#385 Feature/connect to personal wallets

backendenhancementfrontendhelp wanted

Issue #385. First feature PR, please let me know if I mis-used anything. API method that passes parameters into acapy `create-invitation` endpoint, injecting service_name based on application config. and returns the aca-py response directly `{invitationUrl:"",connectionId:""}` Frontend method that makes call on click, and uses qrcode.vue component to render QR code on screen. I'm unsure on the PartnerManager and ConnectionManager relationship, i connected PartnerController directly to ConnectionManager, but this may have been incorrect if you always want it to go through the partnerManager. Issues to fix: - [x] `mvn -f backend/pom.xml test spotbugs:check pmd:check` fails - [ ] After aca-py successfully responds to `connections/create-invitation` it raises an event to the BPA, and the [aca-py client model](https://github.com/boschresearch/aries-acapy-clients/blob/main/java/src/main/java/org/hyperledger/aries/api/connection/ConnectionRecord.java) for that eventhander is too strict in that 'theirLabel' is a required field but is not always provided. _this does not stop the invitation from being used and a connection to be established (it overwrites those values later during the actual connection creation)_

Created At 2021-04-26 20:37:21 +0000 UTC

PR #396	Feature/fix seedhandling

Created At 2021-04-23 13:25:12 +0000 UTC

PR #392	fix helm docu
	Signed-off-by: Frank Bernhardt <Frank.Bernhardt@bosch.com>

Created At 2021-04-22 13:38:36 +0000 UTC

PR #391	Feature/helm agent secrets newnew
	another trial to push these commits ;-) + @Jsyro

Created At 2021-04-22 11:59:38 +0000 UTC

PR #389

Feature/issue credential

Allow a BPA to issue a credential directly to a partner. This is the simplest issuance, and our first step. This assumes that the agents still have auto accept enabled. I don't think this is where all the code will end up, as we will be expanding the issuing capabilities, so I expect major refactoring then. I think we will also need to look at a lot of our existing components that have api calls in them, when perhaps they would be more useful with render only and event hooks for the caller to determine the logic. But we can look at that after we are more feature complete.

Created At 2021-04-20 23:31:14 +0000 UTC