In order to correct another issue, SPS has changed the way how the gateway user information is set. If there was no usermapping policy, the gateway user remained unset and the user was not prompted for a username, therefore the gateway authentication was not attempted and the connections could not pass.
This issue was reported as PAM-8630.
PAM-8630 was fixed, and now if there is no usermapping policy and gateway authentication is enabled, the gateway user defaults to the remote username. Note that it is still possible to overwrite the gateway username by setting it explicitly.
A fix for PAM-8630 was released in SPS maintenance release 5.10.0b, that is available for downloading from the download page.
If you use One Identity-provided plugins, please upgrade them, too, because 5F10 has also changed the way how the gateway user information is populated to plugins, which also also needed to be corrected. The change of the plugins are tracked as PAM-8609.