You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: according the currently implemented concept, the did document is only to be located in portal database (and accessible via portal-backend api), that's the reason why the portal doesn't work out of the box with ssi-dim-wallet-stub, which isn't hosted unter portal-backend domain.
One could think of doing a change to the portal helm chart, essentially providing an option to maintain the entire did document address (domain and path) in the values file, with the exception to the /did.json at the end, which comes from the portal-backend code. IMPORTANT: the default value for the did document baselocation should still be portal-backend address + did document path see in order to follow the implemented concept.
Acceptance Criteria
did document baselocation still defaults to portal-backend address + did document path
in the values.yaml, a parameter dim.didDocumentAddress was introduced which is enabled in the jobs and deployments which currently contain the did document baselocation
only if the dim.didDocumentAddress is filled, it is used else defaulting to current logic (portal-backend address + did document path)
install comments were added to explain this logic (only fill if you want to differ from the default portal-backend address + did document path)
one could also move the didDocumentPath into the jobs and deployments because enabling the option to change that value makes only limited sense considering implementation
Additional Information
detected in v2.3.0
The text was updated successfully, but these errors were encountered:
Description
This issue is the result of the discussion here eclipse-tractusx/tractus-x-umbrella#197 (comment)
Background: according the currently implemented concept, the did document is only to be located in portal database (and accessible via portal-backend api), that's the reason why the portal doesn't work out of the box with ssi-dim-wallet-stub, which isn't hosted unter portal-backend domain.
One could think of doing a change to the portal helm chart, essentially providing an option to maintain the entire did document address (domain and path) in the values file, with the exception to the
/did.json
at the end, which comes from the portal-backend code. IMPORTANT: the default value for the did document baselocation should still be portal-backend address + did document path see in order to follow the implemented concept.Acceptance Criteria
dim.didDocumentAddress
was introduced which is enabled in the jobs and deployments which currently contain the did document baselocationdim.didDocumentAddress
is filled, it is used else defaulting to current logic (portal-backend address + did document path)Additional Information
detected in v2.3.0
The text was updated successfully, but these errors were encountered: