Chat now with support
Chat mit Support

Safeguard for Privileged Sessions On Demand Hosted - Starling Two-Factor Authentication- Tutorial

Configure your Starling 2FA account for SPS

Prerequisites:

  • Administrator access to your Starling 2FA account.

  • Make sure that you have all the required components listed in Technical requirements.

  1. Enable Two-factor Authentication (2FA) for your organization.

    For details on configuring the required methods for two-factor authentication, see Customizing user authentication in the Starling 2FA documentation.

  2. Optional: If you do not use auto-provisioning, add users to your Starling 2FA account.

    The users you want to authenticate with SPS must have an activated account in Starling 2FA. For details on managing your user accounts, see Managing user accounts in the Starling 2FA documentation.

Configure SPS to use Starling Two-factor Authentication

Prerequisites:

  • Administrator access to SPS.

  • Make sure that you have all the required components listed in Technical requirements.

To configure SPS to use Starling Two-factor Authentication

  1. Download the SPS Starling 2FA plugin

    SPS customers can download the official plugin from GitHub.

  2. Upload the plugin to SPS

    Upload the plugin to SPS. For details, see "Using a custom Authentication and Authorization plugin to authenticate on the target hosts" in the Administration Guide.

  3. Configure the plugin on SPS

    The plugin includes a default configuration file, which is an ini-style configuration file with sections and name=value pairs. You can edit it on the Policies > AA Plugin Configurations page of the SPS web interface.

    1. Configure the usermapping settings if needed. SPS must find out which Starling 2FA user belongs to the username of the authenticated connection. For that, it can query your LDAP/Microsoft Active Directory server. For details, see [USERMAPPING].

    2. Configure other parameters of your plugin as needed for your environment. For details, see SPS Starling plugin parameter reference.

  4. Configure a Connection policy and test it

    Configure a Connection policy on SPS. In the AA plugin field of the Connection policy, select the SPS Starling plugin you configured in the previous step, then start a session to test it. For details on how a user can perform multi-factor authentication, see Perform multi-factor authentication with the SPS Starling 2FA plugin in terminal connections and Perform multi-factor authentication with the SPS Starling 2FA plugin in Remote Desktop (RDP) connections.

SPS Starling plugin parameter reference

This section describes the available options of the SPS Starling plugin.

The plugin uses an ini-style configuration file with sections and name=value pairs. This format consists of sections, led by a [section] header and followed by name=value entries. Note that the leading whitespace is removed from values. The values can contain format strings, which refer to other values in the same section. For example, the following section would resolve the %(dir)s value to the value of the dir entry (/var in this case).

[section name]
dirname=%(dir)s/mydirectory
dir=/var

All reference expansions are done on demand. Lines beginning with # or ; are ignored and may be used to provide comments.

You can edit the configuration file from the SPS web interface. The following code snippet is a sample configuration file.

[starling]
timeout=60
rest_poll_interval=1

[starling_auto_provision]
email_attribute=<LDAP-attribute-of-user-email-address>
phone_attribute=<LDAP-attribute-of-user-phone-number>

[auth]
prompt=Press Enter for push notification or type one-time password:
disable_echo=no

[connection_limit by=client_ip_gateway_user]
limit=0

[authentication_cache]
hard_timeout=90
soft_timeout=15
reuse_limit=0

######[WHITELIST]######

[whitelist source=user_list]
name=<name-of-user-list-policy>

[whitelist source=ldap_server_group]
allow=no_user
except=<group-1>,<group-2>

######[USERMAPPING]######

[usermapping source=explicit]
<user-name-1>=<id-1>
<user-name-2>=<id-2>

[usermapping source=ldap_server]
user_attribute=description

[username_transform]
append_domain=<domain-without-@-character>

[ldap_server]
name=<name-of-LDAP-server-policy>

[credential_store]
name=<name-of-credential-store-policy-that-hosts-sensitive-data>

[logging]
log_level=info

[https_proxy]
server=<proxy-server-name-or-ip>
port=3128

[question_1]
key=<name-of-name-value-pair>
prompt=<the-question-itself-in-text>
disable_echo=No

[question_2]...

[starling]

This section contains the options related to your Starling account.

If you are using a Starling 2FA plugin, (that is, you have uploaded it to Basic Settings > Plugins and then configured it at Policies > AA Plugin Configurations) and the SPS node is joined to One Identity Starling, you do not have to specify api_key and api_url in the Starling 2FA plugin configuration. This configuration method is more secure.

[starling]
timeout=60
rest_poll_interval=1
timeout
Type: integer [seconds]
Required: no
Default: 60

Description: How long an HTTP request can take during communication with the Starling server.

rest_poll_interval
Type: integer [seconds]
Required: no
Default: 1

Description: How often the plugin checks the Starling server to see if the push notification was successful.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen