Known issues
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
- There are no known issues for this release.
System requirements
Before using the 20 November 2019 Starling Identity Analytics & Risk Intelligence release, ensure that your system meets the following minimum hardware and software requirements.
Browser requirements
Table 1: Browser requirements
|
Internet Explorer |
Windows 7 |
11 |
|
Google Chrome |
Windows 10
Android
Mac OS X Yosemite |
Latest |
|
Mozilla Firefox |
Windows 8.1 |
Latest |
|
Microsoft Edge |
Windows 10 |
Latest |
|
Safari |
Mac OS X Yosemite
IOS 8 |
See OS/Platform |
|
Opera |
Windows 7
Mac OS X Yosemite |
Latest |
Collector agent requirements
The Starling Identity Analytics & Risk Intelligence collector agent has some additional hardware and software requirements before it can be downloaded:
Table 2: Starling Identity Analytics & Risk Intelligence Collector Agent requirements
|
Operating System |
Minimum requirements:
Windows Server 2008 R2 SP1 x64 |
|
Memory |
8GB |
|
Server Software |
.Net Framework 4.6.1 |
Data source module requirements
Once a collector agent has been installed you can begin configuring data sources modules. The following table shows the requirements based on the type of data source module you are configuring.
Table 3: Starling Identity Analytics & Risk Intelligence data source module requirements
| Active Roles |
ARS 6.9 to 7.x
|
|
IMPORTANT: Although supported, it is strongly recommended that a collector agent not be installed on a machine with an ARS server. |
-
At minimum a domain member account with read access delegated to the following three Active Roles nodes is required: Configuration, Managed Units, and Active Directory.
The Active Directory template All Objects - Read All Properties contains these minimum permissions and can be used. Or you can create a custom template so long as it contains those minimum permissions. See the Active Roles documentation for information on configuring permissions within Active Roles.
|
|
NOTE: By default, Distributed COM Users should contain Authenticated Users. However, if this is missing then you will be unable to connect to Active Roles remotely. For more information, see this article on adding MinARSAdmin or the exact account in order to fix this issue. |
- If both 6.9 and 7.x ADSI providers are available, the ARS 7.x ADSI provider will take precedence followed by 6.9 unless the ActiveRolesAdsiVersion environment variable (in the collector configuration file) has been edited to indicate either 6.9 or 7.0 (which covers all 7.x versions) as the specific version. No other versions can be used as the ActiveRolesAdsiVersion environment variable.
- If no ADSI providers are installed, 6.9 and 7.2.0 ADSI providers will be installed. If an ADSI provider is detected, the collector agent will attempt to use that ADSI provider without installing additional providers.
- When a collector agent is removed, any ADSI providers that were originally installed by the collector agent will also be removed. Any additional dependencies that were installed will not be removed since they are standard Windows redistributables.
- Should an ARS installation not fully meet the supported version requirements for all detected ARS Administration Services, this will cause a version compatibility problem and the collector agent will be unable to collect from that installation.
|
| Active Directory |
- Active Directory credentials are required for configuring the data source module.
- A global catalog must be available in order to resolve trustees outside of the domain.
- A global catalog must be resolvable via its DNS name regardless of whether you are connecting directly to it or to a domain controller connected with a global catalog.
|
| Safeguard |
Safeguard 2.1.0.0 (or greater)
- A Safeguard user with Auditor permissions is required for configuring the data source module.
- The machine running the Safeguard data source module must have the proper SSL root certificate authority certificate(s) that are being used by Safeguard. For more information, see SSL Certificates in the One Identity Safeguard Administration Guide (Safeguard documentation).
|
Product licensing
Use of this software is governed by the Software Transaction Agreement found at http://www.oneidentity.com/legal/sta.aspx and the SaaS Addendum at http://www.oneidentity.com/legal/saas-addendum.aspx. This software does not require an activation or license key to operate.
More resources
Additional information is available from the following:
