-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create Manifest Service #500
Comments
For an MVP implementation we have decided that we will implment the manifest service as a separate service that sits along side the SCS and is access controlled via the EDAPI. This will require a service with the following two end points for the MVP implementation:
|
I think that when we create endpoint 2 described above that the endpoint should validate that the signature is valid which it can do because it can connect out to the OrgRegistry and get the public key for the corresponding GLN and then verify that the sig checks out. |
…an be shared between OR/SCS/Trails.
…an be shared between OR/SCS/Trails.
…tack version as the rest of the codebase.
…py pasting code from the OR to initalise the Trails Service. This issue was identified in code review.
This issue was identified in code review, based on discussion #509 (comment).
…wing to give a more intuative trail entry time ordering expectation. I still don't love this nomenclature because really "previous" means "previous entry" but that would be to verbose and so it doesn't fit, but previously it was getting confusing which direction was parent and child.
…s-haskel so that they can be used across services.
… case style used elsewhere in codebase.
…s of tests and correct where they don't. Have left the debbuging print statements for future use as this has to be a manual process.
This recommendation was made in code review.
No description provided.
The text was updated successfully, but these errors were encountered: