This problem affects the following products:
- HealthShare Unified Care Record: 2022.2 only
A defect in the HS 2022.2 release caused public OAuth 2.0 client configuration to be recreated at the time of Production Start even if the configuration was correct and should not have been recreated.
In some deployments, where a load balancer is configured, the defect caused a Production Start to fail if the load balancer happened to change the routing of the OAuth 2.0 configuration request to a different instance than the one on which the Production was being started.
A short-term workaround is available for customers until they are able to apply the long-term correction in their environment. The workaround for the Production Start failure is to temporarily reconfigure the load balancer to only point to one instance until the Production has been started. After that, the load balancer can be reverted to its typical state.
This has been corrected as of version 2023.1.
The long-term correction for this defect is identified as HSIEO-7278 which will be included in all future product releases. It is also available via ad hoc change file (patch) or full kit distribution by contacting the Worldwide Response Center (WRC).