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

Healthcare settings: Direct endpoint cert/alia (and others) doesn't persist #16

Open
kmarx opened this issue Oct 22, 2024 · 1 comment

Comments

@kmarx
Copy link
Contributor

kmarx commented Oct 22, 2024

In Transport Configuration, Direct Endpoint Certificate Name or Alia is a required field so healthcare settings can't be saved without entering it. However, the entered value doesn't persist on the backend. So, not only does it seem non-functional but it has to be re-entered every time
image
.

@kmarx
Copy link
Contributor Author

kmarx commented Oct 22, 2024

Our recollection is that there are also other fields that have this behavior, but it may require fiddling with true/false settings on other properties to expose the behavior. Please double check. At the very least these fields also don't persist but aren't required so the save completes. Maybe they're not supported yet? But we do use TLS 1.2 in our world.
image

@kmarx kmarx changed the title Healthcare settings: Direct endpoint cert/alia doesn't persist Healthcare settings: Direct endpoint cert/alia (and others) doesn't persist Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant