In order to use Starling Two-Factor Authentication with Safeguard Authentication Services, you will need the following:
-
A valid license for Safeguard Authentication Services.
-
A Starling Organization Admin account or a Collaborator account. For more information on Starling, see the One Identity Starling Hosted User Guide.
-
An Active Directory group for Starling users.
NOTE: All Starling users must have the following defined in order to work with Starling 2FA:
-
Valid email address
-
Valid mobile phone number in E.164 format. (that is, +<country code><area code><phone number>)
-
Be a member of this Starling group dictated by GPO.
For more information, see Setting up Starling users..
-
Safeguard Authentication Services 4.2 (or later)
The following table provides a list of supported platforms for integrating Safeguard Authentication Services with Starling Two-Factor Authentication.
NOTE: PPC64 and PPC64LE architectures require a kernel greater than 2.6.37.
Table 20: Starling 2FA: Supported platforms
|
CentOS Linux |
5, 6, 7, 8 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, IA-64, x86, x86_64, AARCH64 |
|
Debian |
Current supported releases |
x86_64, x86, AARCH64 |
|
Fedora Linux |
Current supported releases |
x86_64, x86, AARCH64 |
|
FreeBSD |
10.x, 11.x |
x32, x64 |
|
IBM AIX |
7.1, 7.2 |
Power 4+ |
|
OpenSuSE |
Current supported releases |
x86_64, x86, AARCH64 |
|
Oracle Enterprise Linux (OEL) |
5, 6, 7, 8 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, IA-64, x86, x86_64, AARCH64 |
|
Oracle Solaris |
10 8/11,
11.x |
SPARC, x64 |
|
Red Hat Enterprise Linux (RHEL) |
5, 6, 7, 8 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, IA-64, x86, x86_64, AARCH64 |
|
SuSE Linux Enterprise Server (SLES)/Workstation |
11, 12, 15 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, IA-64, x86, x86_64, AARCH64 |
|
Ubuntu |
Current supported releases |
x86_64, x86, AARCH64 |
A new Group Policy Object has been added to Safeguard Authentication Services to manage the group file for Starling, which is located in /etc/opt/quest/vas/users.starling.
Sample users.starling file
# This assumes that the host has been joined to the example.com domain.
# To validate the users.starling file, run:
# vastool info acl
#
# This file controls which user's have Starling appled to them during login based
# on group membership.
# For entries:
# If DOMAIN is omitted ( simple name given )it is assumed to be the joined domain.
# Entries are case insensitive.
# DOMAIN can be either long(fqdn) or short(netbios).
# Apply Starling to members of the sales and engineering groups.
# The entry DOMAIN\SamAccountName format is preferred.
EXAMPLE\sales
engineering
This file can be manually created or set using the GPO.
To enable Starling for users using the GPO
- Open your Group Policy management system.
- Select the applicable group policy.
- Navigate to Computer configuration | Unix Settings | Starling.
- Double-click users.starling.
- Add the groups that contain the users to be enabled to use Starling 2FA.
It may take up to 90 minutes to apply this configuration change. Use vgptool apply to apply the changes quicker.
Joining Safeguard Authentication Services to Starling allows you to use features from Starling Two-Factor Authentication.
To join Safeguard Authentication Services with Starling
- From the Control Center, navigate to Preferences | Starling Two-Factor Authentication.
- In the Join to Starling and enable Two-Factor Authentication pane, click Starling Join Settings.
-
On the Starling Two-Factor Authentication dialog, use the Product TIMs drop-down to select a valid Safeguard Authentication Services license.
NOTE: The other fields on this dialog are read-only and contain the following information after you successfully join to Starling:
- Product Name: Displays Safeguard Authentication Services.
- Product Instance: Displays the unique identifier for Starling.
-
Click Join to Starling.
NOTE: The following additional information may be required:
- If you do not have an existing session with Starling, you will be prompted to authenticate.
- If your Starling account belongs to multiple organizations, you will be prompted to select which organization Safeguard Authentication Services will be joined with.
After the join has successfully completed, you will be returned to the Safeguard Authentication Services Control Center and the Join to Starling and enable Two-Factor Authentication pane will display the following:
- Product Instance: Displays the unique identifier for Starling. You can click the Copy button to the right of this field to copy the product instance identifier to your desktop.
- Starling Join State: Displays either Joined or Unjoined.
The Starling Proxy Settings must be configured if your company policies do not allow devices to connect directly to the web. Once configured, Safeguard Authentication Services uses the configured proxy server for outbound web requests to Starling.
NOTE: One Identity recommends you use an automatic configuration script (proxy PAC file). To specify a previously configured PAC file, select the Use automatic configuration script check box and enter the address of the proxy.pac file.
To configure Starling to use a proxy server
- From the Control Center, navigate to Preferences | Starling Two-Factor Authentication.
- In the Starling Proxy Configuration pane, click Starling Proxy Settings.
-
On the Starling Proxy Configuration dialog, enter the following information about the proxy server to be used:
To specify a previously configured PAC file (recommended):
- Use automatic configuration script: Select this check box.
- Address: Enter the address of the proxy.pac file.
To use username/password to specify the proxy server:
- Click OK to save your selections.
