|RAD-179||SonicWall NetExtender created a hotfix to resolve a RADIUS client problem with 2FA methods. All 2FA methods are available.|
|Editing and saving a disabled realm no longer enables the realm.|
|RAD-204||The Static Value field is empty by default in the RADIUS Client tab, in the Static Value Mapping section.|
|RAD-206||The Static Value field allows up to 247 characters in the RADIUS Client tab, in the Static Value Mapping section.|
|RAD-208||Uppercase letters are allowed in the Static Value field, in the RADIUS Client tab, in the Static Value Mapping section.|
|RAD-212||Clicking the context-sensitive help (small i) over a disabled client setting shows information for disabled clients in the RADIUS Client tab.|
|RAD-249||Numerous minor bug fixes were completed.|
When creating a RADIUS client and clicking the Add Attribute button, the client is no longer saved when the Add Client button is not selected.
|RAD-253||RADIUS client attribute values are restricted to the supported RADIUS protocol length of 253 bytes.|
When running the RADIUS client with the Pulse Secure client and 2FA options, Pulse Secure limits the maximum number of characters to 210. End-users can see all options in the Pulse Secure web client when the number of characters is less than 210.
A second Pulse Secure limitation causes options 5 - 8 to be cut off from end-users' view on the 2FA list. End-users can select options 5 - 8, even though they are off-screen and there is no scrollbar.
Optionally, modify text in the RADIUS uiTextsBundle.properties configuration file to shorten messages from the multi-factors message. See "Modify text showing on client user interface during login" in Configuration guide - v2.5 - SecureAuth IdP RADIUS server.
Invalid characters in user IDs sent to the RADIUS server cause a RADIUS server failure.
Workaround: Ensure that user IDs contain the following valid characters only:
New features and enhancements