Duo integrates with your PeopleSoft application to add two-factor authentication to portal logins by protecting LDAP connections. In this type of configuration, users will receive an automatic push or phone callback during login. Users who need to use a passcode have the option to append it to their existing password when logging in.
This configuration doesn't support inline self-service enrollment. You'll need to create your users in Duo ahead of time using one of our other enrollment methods, like directory sync or CSV import. Read the enrollment documentation to learn more.
Duo integrates with GreyHeller's ERP Firewall - a rules-based engine for securing PeopleSoft access. Learn more about how Duo and GrayHeller protect your organization's sensitive information.
This integration communicates with Duo's service on TCP port 443. Also, we do not recommend locking down your firewall to individual IP addresses, since these may change over time to maintain our service's high availability.
To integrate Duo with your PeopleSoft environment, you will need to install a local proxy service on a machine within your network. Before proceeding, you should locate (or set up) a system on which you will install the Duo Authentication Proxy. The proxy supports Windows and Linux systems (in particular, we recommend Windows Server 2012 R2 or later, Red Hat Enterprise Linux 6 or later, CentOS 6 or later, or Debian 6 or later).
Then you'll need to:
The security of your Duo application is tied to the security of your secret key (skey). Secure it as you would any sensitive credential. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
The Duo Authentication Proxy can be installed on a physical or virtual host. We recommend a system with at least 1 CPU, 200 MB disk space, and 4 GB RAM (although 1 GB RAM is usually sufficient).
Ensure that OpenSSL, Python 2.6 or 2.7 (including development headers and libraries), and a compiler toolchain are installed. On most recent RPM-based distributions — like Fedora, RedHat Enterprise, and CentOS — you can install these by running (as root):
$ yum install gcc make openssl-devel python-devel libffi-devel
On Debian-derived systems, install these dependencies by running (as root):
$ apt-get install build-essential libssl-dev python-dev libffi-dev
To ensure that your Python version will work with the Authentication Proxy, run:
$ python --version
If the output does not say "Python 2.6.x" or "Python 2.7.x", first take note that many distributions can support multiple versions of python simultaneously. If your python installation does not appear to be a supported version, try replacing "python" in the above command with "python2.6" or "python2.7". If neither of these work, then you will need to install a different version of Python. You may need to search additional repositories for your distribution (e.g. for Centos or Red Hat Enterprise Linux, Extra Packages for Enterprise Linux), or build Python from source.
Download the most recent Authentication Proxy for Unix from https://dl.duosecurity.com/duoauthproxy-latest-src.tgz. Depending on your download method, the actual filename may reflect the version e.g. duoauthproxy-2.9.0-src.tgz. View checksums for Duo downloads here.
Extract the Authentication Proxy files and build it as follows:
Where python_command is the command to run a Python 2.6 or Python 2.7 interpreter (e.g. "python", "python2.6", "python2.7").
$ tar xzf duoauthproxy-latest-src.tgz $ cd duoauthproxy-version-src $ export PYTHON=python_command $ make
Install the authentication proxy (as root):
$ cd duoauthproxy-build $ ./install
Follow the prompts to complete the installation.
The proxy listensfor connections on ports 389 and 636 by default. Privileged ports below 1024 are reserved for the root user. Therefore, the proxy will not start if you choose any user account other than "root" to run under during installation.
If you ever need to uninstall the proxy, run
After the installation completes, you will need to configure the proxy.
The Duo Authentication Proxy configuration file is named authproxy.cfg, and is located in the conf subdirectory of the proxy installation. With default installation paths, the proxy configuration file will be located at:
|Platform||Default Configuration Path|
|Windows (64-bit)||C:\Program Files (x86)\Duo Security Authentication Proxy\conf\authproxy.cfg|
|Windows (32-bit)||C:\Program Files\Duo Security Authentication Proxy\conf\authproxy.cfg|
The configuration file is formatted as a simple INI file. Section headings appear as:
Individual properties beneath a section appear as:
The Authentication Proxy may include an existing authproxy.cfg with some example content. For the purposes of these instructions, however, you should delete the existing content and start with a blank text file. We recommend using WordPad or another text editor instead of Notepad when editing the config file on Windows.
In this step, you'll set up the Proxy's primary authenticator — the system which will validate users' existing passwords. In most cases, this means configuring the Proxy to communicate with Active Directory.
To use Active Directory as your primary authenticator, add an
[ad_client] section to the top of your config file. Add the following properties to the section:
||The hostname or IP address of your domain controller.|
||The username of a domain member account that has permission to bind to your Active Directory and perform searches. We recommend creating a service account that has read-only access.|
The password corresponding to
The LDAP distinguished name (DN) of an Active Directory container or organizational unit (OU) containing all of the users you wish to permit to log in. For example:
The hostname or IP address of a secondary/fallback domain controller. You can add additional domain controllers as
To further restrict access, specify the LDAP distinguished name (DN) of a security group that contains the users who should be able to log in. Other users will not pass primary authentication. For example:
[ad_client] host=22.214.171.124 host_2=126.96.36.199 service_account_username=duoservice service_account_password=password1 search_dn=DC=example,DC=com security_group_dn=CN=DuoVPNUsers,OU=Groups,DC=example,DC=com
For advanced Active Directory configuration, see the full Authentication Proxy documentation.
Next, you need to set up the Authentication Proxy to handle LDAP authentication requests. To do so, create a ldap_server_auto section with the following properties:
||Your API hostname (i.e. api-XXXXXXXX.duosecurity.com)|
||Your integration key|
||Your secret key|
The mechanism that the Authentication Proxy should use to perform primary authentication. This should correspond with a "client" section elsewhere in the config file.
This parameter is optional if you only have one "client" section. If you have multiple, each "server" section should specify which "client" to use.
Either safe or secure:
Path to PEM-formatted SSL/TLS server certificate. Both ssl_key_path and ssl_cert_path must be specified to listen for STARTTLS or LDAPS requests.
Path to PEM-formatted SSL/TLS private key. Both ssl_key_path and ssl_cert_path must be specified to listen for STARTTLS or LDAPS requests.
Specify the DN of the service account used to authenticate from PeopleSoft to the Authentication Proxy. Multi-factor authentication is not required for this user. This setting is needed because PeopleSoft first connects to the Authentication Proxy as the service account user, disconnects, and then authenticates the user who is logging in with a separate LDAP connection. All other accounts will require Duo authentication.
Set this value to 'false'. This setting, when combined with the exempt_ou_1 setting above, ensures that the PeopleSoft service account's initial bind to the Authentication Proxy does not require two-factor authentication.
Set this value to 'false' so that the incoming LDAP connection from PeopleSoft is disconnected immediately after a successful bind. Defaults to 'true', which keeps the LDAP connection open after a successful bind to allow additional queries. The session is closed upon receiving a subsequent bind request. Requires Authentication Proxy version 2.4.14.
Additional OUs or DNs to exempt from multi-factor authentication. Specified as exempt_ou_2, exempt_ou_3, etc.
A completed config file, using Active Directory as the primary authenticator, should look something like:
[ad_client] host=188.8.131.52 service_account_username=ServiceAcct service_account_password=Password1 search_dn=cn=Users,dc=example,dc=com [ldap_server_auto] ikey=DIXXXXXXXXXXXXXXXXXX skey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX api_host=api-XXXXXXXX.duosecurity.com failmode=safe ssl_key_path=ldap_server.key ssl_cert_path=ldap_server.pem exempt_primary_bind=false exempt_ou_1=CN=ServiceAcct,CN=users,DC=example,DC=com allow_searches_after_bind=false
Make sure to save your configuration file when done.
Open an Administrator command prompt and run:
net start DuoAuthProxy
Alternatvely, open the Windows Services console (services.msc), locate "Duo Security Authentication Proxy Service" in the list of services, and click the Start Service button.
If the service starts successfully, Authentication Proxy service output is written to the authproxy.log file, which can be found in the log subdirectory.
If you see an error saying that the "service could not be started", open the Application Event Viewer and look for an Error from the source "DuoAuthProxy". The traceback may include a "ConfigError" that can help you find the source of the issue.
Stop and restart the Authentication Proxy service by either clicking the Restart Service button in the Windows Services console or issuing these commands from an Administrator command prompt:
net stop DuoAuthProxy & net start DuoAuthProxy
Open a root shell and run:
# /opt/duoauthproxy/bin/authproxyctl start
To ensure the proxy started successfully, run:
# /opt/duoauthproxy/bin/authproxyctl status
Authentication Proxy service output is written to the authproxy.log file, which can be found in the log subdirectory.
To stop and restart the Authentication Proxy, open a root shell and run:
# /opt/duoauthproxy/bin/authproxyctl restart
If you modify your
authproxy.cfg configuration after initial setup, you'll need to stop and restart the Duo Authentication Proxy service or process for your change to take effect.
Access the "Configure Directory - Directory Setup" page (select "PeopleTools", then select "Security", then select "Directory", then select "Configure Directory" and click the "Directory Setup" tab).
Enter the following information:
Enter a name for the Duo LDAP directory.
Select 'Microsoft Active Directory' in the drop-down list.
|Default Connect DN||
Enter the distinguished name of the service account used to bind to your Duo Authentication Proxy. This should match the DN configured as exempt_ou_1 in the Authentication Proxy LDAP configuration above.
The service account password.
The IP address or fully-qualified DNS host name of your Duo Authentication Proxy server.
Duo Authentication Proxy server port for incoming LDAP requests. Default port is '389' for CLEAR and STARTTLS and '636' for LDAPS.
If using STARTTLS or LDAPS then the ssl_cert_path and ssl_key_path options must be configured in the Authentication Proxy LDAP configuration above.
After creating the Duo directory, select "Authentication Map" from the "Directory" page.
Select the Directory ID of the Duo directory you just created. The "Connect DN", "Search Base", and "Search Attribute" values should automatically populate. Update the "Search Attribute" from the default attribute to whatever attribute matches the Duo username if necessary. Otherwise, save the new authentication map.
To test your setup, attempt to log in to your newly-configured system as a user enrolled in Duo with an authentication device. When you enter your username and password, you will receive an automatic push or phone callback. Alternatively you can add a comma (",") to the end of your password, followed by a Duo passcode.
For example, given a username 'bob', with password 'password123' and a Duo passcode '123456', you would enter:
username: bob password: password123,123456
In addition, you may also enter the name of an out-of-band factor in lieu of a passcode. You may choose from the following factor names:
Perform Duo Push authentication
You can use Duo Push if you've installed Duo Mobile and added your account to it
|phone||Perform phone callback authentication|
Send a new batch of SMS passcodes
Your authentication attempt will be denied. You can then authenticate with one of the newly-delivered passcodes.
Returning to the previous example, if you wanted to use Duo Push (rather than a passcode) to authenticate, you would enter:
username: bob password: password123,push
You can also specify a number after the factor name if you have more than one device enrolled. So you can enter phone2 or push2 if you have two phones enrolled.