Chat now with support
Chat mit Support

Safeguard Authentication Services 5.0.2 - Evaluation Guide

Privileged Access Suite for Unix Introducing One Identity Safeguard Authentication Services Installing and configuring Safeguard Authentication Services Getting started with Safeguard Authentication Services
Getting acquainted with the Control Center Learning the basics

Enabling debug logging on Windows

To enable debug logging for all Safeguard Authentication Services Windows components

  1. Open Control Center and click Preferences on the left navigation pane.
  2. Expand the Logging Options section.
  3. Open the Log level drop-down menu and set the log level to Debug.

    Debug generates the most log output. Higher levels generate less output. You can set the Log level to Disabled to disable logging.

  4. Click to specify a folder location where you want to write the log files.

    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.

Starling Two-Factor Authentication

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 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:

  • Visit us Online displays the Starling login page where you can create a new Starling account. This help link is available on both dialogs.
  • Trouble Joining displays the Starling support page with information on the requirements and process for joining with Starling. This help link is available on the Starling Two-Factor Authentication dialog.
  • Trouble With Proxy displays the Starling support page with additional information on troubleshooting the proxy configuration. This help link is available on the Starling Proxy Configuration dialog.

Starling Two-Factor Authentication requirements

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 19: Starling 2FA: Supported platforms

Platform

Version

Architecture

CentOS Linux

5, 6, 7, 8

Current Linux architectures: s390, s390x, PPC64, PPC64le, ia64, 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, 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

Current supported releases

x86_64, x86, AARCH64

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen