These release notes provide information about the One Identity Starling Two-Factor RADIUS Agent release.
New features in Starling Two-Factor RADIUS Agent 7.0:
The following is a list of enhancements implemented in Starling Two-Factor RADIUS Agent 7.0.
|You can now connect your RADIUS Agent instance directly to your Starling account.||28668|
The following is a list of issues addressed in this release.
|Resolved Issue||Issue ID|
In the DEBUG mode, the NullReferenceException error is displayed when unrecognized attributes are present.
Active Directory User Repository settings are not validated if the Domain Name, User Name, or Password are invalid.
|Entering Base DN as dc=quest, dc=com does not work. The Base DN field in the Starling Two-Factor Radius Agent Configuration tool is case - sensitive.||24872|
|Simultaneously, logging in to radius agent stops the Starling Two-Factor Radius Agent service.||26342|
|Logging in to the Radius Client tool with custom attribute Address Value Pair : Calling-Station-Id has an issue||27422|
|Temporary Response from the 2FA dashboard does not get parsed as an OTP.||27574|
The following is a list of issues known to exist at the time of release.
|Known Issue||Issue ID|
Logging in to the Radius Client tool, with the shared secret key having Non-ASCII characters, is an issue
Do not configure the shared secret key with Non-ASCII characters.
Before installing Starling Two-Factor RADIUS Agent 7.0, ensure that your system meets the following minimum requirements. You can install Starling Two-Factor RADIUS Agent on physical computers or virtual machines.
|Processor||1.4 GHz or faster, x64 architecture|
|Memory (RAM)||4 GB|
|Hard disk space||50 MB or more|
|Microsoft .NET Framework||Microsoft .NET Framework 4.6.1 or later|
This product does not require licensing.
For installation instructions, see One Identity Starling Two-Factor RADIUS Agent Administrator Guide.
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).