RELEASED: Public: March 6, 2024
Resolved issues
- Operations center single sign-on broken in Java 17 when using an authenticated proxy (BEE-46548)
-
When running a connected controller in 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, under these conditions, the proxy configuration are ignored and the controller will contact the operations center directly regardless of proxy settings.
Note that saving the proxy configuration in the GUI currently saves a blank username. This will be fixed in a future release. If you configure the proxy via CasC, it does not enable authentication unless a username is defined.