Specifications

Resolved Issues  11
Steel-Belted Radius v6.1.1 Release Notes
 Large Windows domain (Windows only)—If your Windows domain has
thousands of users and you click Add in the Administrators panel, SBR
Administrator may take many minutes for the available usernames to appear.
During this time, the Steel-Belted Radius server does not respond to other
copies of the SBR Administrator.
To avoid this problem, create a local Windows group with a name such as
sbradmins. Add this group to access.ini. Restart Steel-Belted Radius. Add
administrators to the
sbradmins group. (8480)
 EAP Methods panel—If you go to the EAP Methods panel, make a change, and
then go elsewhere, an Unexpected Error message may appear. If this occurs,
return to the EAP Methods panel, click Refresh, and verify that your changes
appear correctly. (8454)
 Problems deploying SBR Administrator—If you start up the SBR Administrator
normally - especially with a new version or a new server, you may occasionally
see a
deployer.exe has encountered a problem and needs to close or invalid
signature
error message. (8294)
If you are running the SBR Administrator on Windows:
1. Exit all copies of your Web browser,
2. Open a Windows file browser,
3. In the address bar, enter
%APPDATA%,
4. Double-click
Juniper Networks,
5. Select
WebDeployer and delete it.
If running SBR Administrator on Solaris or Linux:
1. Exit all copies of your Web browser,
2. In a shell, enter
rm -rf ~/.junipernetworks/WebDeployer
 Secondary Authentication—If you check Include Certificate Information
under the Secondary Authentication tab for the EAP-TLS helper authentication
method, then the related Funk VSAs Funk-Peer-Cert-Hash, Funk-Peer-Cert-Issue,
Funk-Peer-Cert-Principal, and Funk-Peer-Cert-Subject are not added to the
request. To resolve the problem, edit the
$RADIUSDIR/system/translators/tlsauth.eap.xml file to read <object
id="Include_Certificate_Info" type="boolean" default="false”
(249799, old
ID-8757)
 Admin root certificates—If you import a root certificate with a key size larger
than 2048 is imported, the SBR Administrator reports that the certificate is
invalid. If this occurs, place the certificate in the ROOT directory; it won't show
up in SBR Administrator, but it will be available for use by TLS and TTLS.(8754)