Implement changes to REST functionality #14387
Labels
engineering
Work to be completed by an engineer
onboarding-ops
Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.
Problem statement
REST does not currently have the ability to send "keys" in the body of the message (for ELIMS) and ability to authenticate with JKS certificates (for CA).
What you need to know
ELIMS requires we send shared key in the body of the message and doesn't need any other other form of authentication.
ELIMS implementation guide:
ELIMS WebServicesHub API Integration Guide.docx
CA only requires that we only authenticate via JKS certificate no other form of authentication is necessary.
Our REST transport currently assumes OAuth is needed for all receivers. We need to re-work that logic to only do OAuth when necessary.
Acceptance Criteria
ReportStream can send keys in body of the message via RestTransport
ReportStream can authenticate using JKS certificate
Documentation is updated on how to create credentials for these new types of authentication
Ensure changes don't break existing REST receivers
Blocking Add ELIMS as REST reciever #14170 Update CA to use REST instead of SFTP #14108
The text was updated successfully, but these errors were encountered: