RELEASED: Public: March 6, 2024
Resolved issues
- Operations center single sign-on broken on Java 17 when using an authenticated proxy (BEE-46548)
-
When you run a connected controller on Java 17 with a proxy configured with username/password authentication, the operations center single sign-on did not work due to a limitation in a Java HTTP client. Now, the proxy configuration is ignored and the controller contracts the operations center directly regardless of the proxy settings.
| When you save the proxy configuration in the GUI, it currently saves a blank username. This will be fixed in a future release. When you configure the proxy via Configuration as Code, it does not enable authentication unless a username is actually defined. |