From ea6dfd7123e9057e964d406837957a056bc1852f Mon Sep 17 00:00:00 2001 From: Britta Stallknecht Date: Tue, 31 Oct 2023 16:33:15 +0000 Subject: [PATCH] fix: diagram prepare onboarding package (cherry picked from commit 7d0548792615be377b080c0cf02d554b26fb30ff) --- .../integrate/prepare-enmeshed-onboarding-package.md | 8 ++++---- .../integrate/Prepare enmeshed onboarding package.svg | 1 - assets/images/integrate/Prepare onboarding package.svg | 1 + 3 files changed, 5 insertions(+), 5 deletions(-) delete mode 100644 assets/images/integrate/Prepare enmeshed onboarding package.svg create mode 100644 assets/images/integrate/Prepare onboarding package.svg diff --git a/_includes/scenarios/integrate/prepare-enmeshed-onboarding-package.md b/_includes/scenarios/integrate/prepare-enmeshed-onboarding-package.md index 9b4fdcdb4..1b74f47b2 100644 --- a/_includes/scenarios/integrate/prepare-enmeshed-onboarding-package.md +++ b/_includes/scenarios/integrate/prepare-enmeshed-onboarding-package.md @@ -69,7 +69,7 @@ If you have successfully created the RelationshipTemplate on your Connector on a ... }, "truncatedReference": "", - "maxNumberOfAllocations": "", + "maxNumberOfAllocations": , "secretKey": "" } } @@ -84,13 +84,13 @@ Before an Identity can establish a Relationship with your Connector, it must sen - Onboarding of an App user: Scan the QR Code of the RelationshipTemplate. - Onboarding of another Connector: Load the RelationshipTemplate onto it. -[![High level architecture diagram of enmeshed components and layers]({{ '/assets/images/integrate/Prepare enmeshed onboarding package.svg' | relative_url }}){: .align-center}]({{ '/assets/images/integrate/Prepare enmeshed onboarding package.svg' | relative_url }}) +[![High level architecture diagram of enmeshed components and layers]({{ '/assets/images/integrate/Prepare onboarding package.svg' | relative_url }}){: .align-center}]({{ '/assets/images/integrate/Prepare onboarding package.svg' | relative_url }}) ### Onboarding of an App user -If an App user wants to send a Relationship Request to your Connector, the App user must first scan a QR Code that contains the reference to a RelationshipTemplate owned by your Connector. By sending the Request `GET /api/v2/RelationshipTemplates/{id}`, specifying the value `image/png` in the `Accept` header field, you can create this QR Code on your Connector. You must replace the placeholder `{id}` in the URL with the ID of the RelationshipTemplate obtained from the [success response]({% link _docs_integrate/prepare-enmeshed-onboarding-package.md %}#success-response) above. +If an App user wants to send a Relationship Request to your Connector, the App user must first scan a QR Code that contains the reference to a RelationshipTemplate owned by your Connector. By sending the Request `GET /api/v2/RelationshipTemplates/`, specifying the value `image/png` in the `Accept` header field, you can create this QR Code on your Connector. You must replace the placeholder `` in the URL with the ID of the RelationshipTemplate obtained from the [success response]({% link _docs_integrate/prepare-enmeshed-onboarding-package.md %}#success-response) above. For more details on how to send a Request to create a QR Code containing the reference to a RelationshipTemplate, see the description of the [Get RelationshipTemplate]({% link _docs_use-cases/use-case-transport-get-relationship-template.md %}) usecase. {: .notice--info} @@ -121,7 +121,7 @@ In doing so, it is necessary to insert the value of the `truncatedReference` pro For more details on how to send a Request to load a RelationshipTemplate created by a Connector onto another Connector, see the description of the [Load RelationshipTemplate created by others]({% link _docs_use-cases/use-case-transport-load-relationship-template-created-by-others.md %}) usecase. {: .notice--info} -When the RelationshipTemplate of your Connector is successfully loaded onto the other Connector, a success response is sent. Assuming that there is no Relationship between the two Connectors yet, the other Connector will additionally receive an internally created new incoming Request. The user of the other Connector can accept it if it is wanted to send a Relationship Request to your Connector. +When the RelationshipTemplate of your Connector is successfully loaded onto the other Connector, a success response is sent. This looks like the above [success response]({% link _docs_integrate/prepare-enmeshed-onboarding-package.md %}#success-response) except that the value of the property `isOwn` is now `false` instead of `true`. Assuming that there is no Relationship between the two Connectors yet, the other Connector will additionally receive an internally created new incoming Request. The user of the other Connector can accept it if it is wanted to send a Relationship Request to your Connector. ## What's next? diff --git a/assets/images/integrate/Prepare enmeshed onboarding package.svg b/assets/images/integrate/Prepare enmeshed onboarding package.svg deleted file mode 100644 index bb13f119a..000000000 --- a/assets/images/integrate/Prepare enmeshed onboarding package.svg +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/assets/images/integrate/Prepare onboarding package.svg b/assets/images/integrate/Prepare onboarding package.svg new file mode 100644 index 000000000..d968e177d --- /dev/null +++ b/assets/images/integrate/Prepare onboarding package.svg @@ -0,0 +1 @@ + \ No newline at end of file