Skip to content
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

Move Flexion senders and receivers to production #15991

Closed
oslynn opened this issue Sep 24, 2024 · 4 comments
Closed

Move Flexion senders and receivers to production #15991

oslynn opened this issue Sep 24, 2024 · 4 comments
Assignees
Labels
onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.

Comments

@oslynn
Copy link
Collaborator

oslynn commented Sep 24, 2024

Moving Flexion senders (e.g. simulated-hospital, simulated-lab, etor-service-sender) and receivers (e.g. simulated-hospital, etor-service-receiver-orders, etor-service-receiver-results) to production.
1.) Update setting for all senders and receivers
2.) Test connectivity

@oslynn oslynn added the onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. label Sep 24, 2024
@oslynn oslynn self-assigned this Sep 24, 2024
@oslynn
Copy link
Collaborator Author

oslynn commented Sep 24, 2024

We are in testing phase.

@oslynn
Copy link
Collaborator Author

oslynn commented Sep 25, 2024

Debug authentication issue:
@ott SATHNGAM
We're attempting to send a hl7 ORU message to RS Prod from flexion.simulated-hospital which is being routed to flexion.etor-service-receiver-results . It is seemingly failing after the ITEM_ROUTED step and not actually being delivered to TI (as we are not seeing any TI logs in production). Here is the id: "reportId": "2f3da661-41b1-4132-a1f6-4b39417a3b3e" . Are you able to help troubleshoot this with us?

image.png

The messages are being routed, but failing to send:
Send function unrecoverable exception: Rollback caused Event: {"type":"report","eventAction":"SEND","emptyBatch":false,"reportId":"3e892b18-c8ec-4cf6-b24e-acbb52163a35","at":"","messageQueueName":"send"}
https://portal.azure.com/#view/AppInsightsExtension/DetailsV2Blade/ComponentId~/%7B%2[…]0%2C%22endTime%22%3A%222024-09-24T23%3A22%3A25.685Z%22%7D%7D
It seems to be an issue with the key
image.png

image.png

@oslynn
Copy link
Collaborator Author

oslynn commented Sep 26, 2024

Due to RS can only handle PKCS#1 key files (BEGIN RSA PRIVATE KEY) come from the PEM encrypted messaging project, it causes issue when it try to read from the vault. I happened to create the key pair for PKCS#8 and registered in the vault. Therefore, it can't handle it. I generated the new set of PKCS#1 gave them new public key and register the private key in the vault and now it is good to go.

@oslynn
Copy link
Collaborator Author

oslynn commented Oct 8, 2024

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.
Projects
None yet
Development

No branches or pull requests

2 participants