To enable debug logging for all Safeguard Authentication Services Windows components
Debug generates the most log output. Higher levels generate less output. You can set the Log level to Disabled to disable logging.
Safeguard Authentication Services Windows components log information into the specified log folder the next time they are loaded. Each component logs to a text file named after the DLL or EXE that generates the log message.
From the Control Center, select Preferences then Starling Two-Factor Authentication to view and update configurations.
The following sections provide a comprehensive look at Starling Two-Factor Authentication.
From Preferences | Starling Two-Factor Authenticationyou can perform these actions.
For more details on Starling Two-Factor Authentication, see the Safeguard Authentication Services Administration Guide, One Identity Starling Integration.
One Identity Starling Two-Factor Authentication is a SaaS solution that provides two-factor authentication on a product enabling organizations to quickly and easily verify a user's identity. This service is provided as part of the One Identity Starling cloud platform. Joining Safeguard Authentication Services to One Identity Starling allows you to take advantage of these companion features from Starling services. For more information on Starling, see the One Identity Starling User Guide.
In order to use Starling 2FA with Safeguard Authentication Services, you must join Safeguard Authentication Services to Starling. This is done from the Preferences | Starling Two-Factor Authentication pane in the Control Center. From this pane, you can also configure Starling to use a proxy server and customize the attributes to be used in push notifications.
Help links that provide assistance with Starling are available on the dialogs displayed when setting up the Starling Join Settings or Starling Proxy Settings:
In order to use Starling Two-Factor Authentication with Safeguard Authentication Services, you will need the following:
An Active Directory group for Starling users.
NOTE: All Starling users must have the following defined in order to work with Starling 2FA:
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.
Platform |
Version |
Architecture |
---|---|---|
CentOS Linux |
5, 6, 7, 8 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, ia64, x86, x86_64, AARCH64 |
Debian |
x86_64, x86, AARCH64 | |
Fedora Linux |
x86_64, x86, AARCH64 | |
FreeBSD |
10.x, 11.x |
x32, x64 |
IBM AIX |
7.1, 7.2 |
Power 4+ |
OpenSuSE |
x86_64, x86, AARCH64 | |
Oracle Enterprise Linux (OEL) |
5, 6, 7, 8 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, ia64, 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, ia64, x86, x86_64, AARCH64 |
SuSE Linux Enterprise Server (SLES)/Workstation |
11, 12, 15 |
Current Linux architectures: s390, s390x, PPC64, PPC64le, ia64, x86, x86_64, AARCH64 |
Ubuntu |
x86_64, x86, AARCH64 |
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center