Supported authentication
methodsThis technical integration guide describes how to integrate a PAM RADIUS Plug-in and Identity as a Service. Although this document specifically covers the PAM RADIUS Plug-in, the information provided applies to all Redhat Linux 8, 9. The aim of this integration is to provide strong, second-factor authentication for your PAM RADIUS Plug-in solution using Identity as a Service.
The PAM RADIUS Plug-in supports the Identity as a Service authentication methods and authentication protocols listed in the table below. The capabilities may depend on the Identity as a Service configuration, or the set up of other third party authentication resources (Active Directory, for example).
Before you begin, review the following:
Supported authentication
methods| Authentication method | Notes | Supported protocols |
| Password | Password authentication is first-factor authentication with Identity as a Service password feature. |
PAP |
| RADIUS | RADIUS authentication is first-factor authentication with a RADIUS server. |
PAP |
| External | External authentication is first-factor authentication with a RADIUS server. |
PAP |
| Grid | Two-step authentication only |
PAP |
| Token | Identity as a Service supports response-only tokens. One-step or two-step authentication (including push authentication). |
PAP |
Temporary Access Code |
Token authentication must be configured. | PAP |
OTP (One Time Password) by SMS or Token |
Two-step authentication only | PAP |
Note: The PA-VM supports only PAP authentication methods with RADIUS.
PrerequisitesComplete the following steps before integrating your authentication system with Identity as a Service:
1. Install and configure your first-factor authentication resource using the documentation provided by the vendor. The first-factor authentication resource can be a RADIUS server or an external authentication resource (a Local DB, LDAP-compliant directory or Windows domain controller through Kerberos).
2. Install and configure the RADIUS appliance using the documentation provided by the vendor. The device must be able to route traffic before integrating with Identity as a Service.
3. Install and configure Identity as a Service and an Identity as a Service gateway (containing a RADIUS proxy agent). Take note of the shared secrets, IP addresses, and ports you use. You need this information to configure the RADIUS appliance and first-factor authentication resource. See Create and configure a Gateway.
4. If you want to configure your RADIUS appliance and first-factor authentication resource to recognize Identity as a Service user groups, you must define the Identity as a Service user groups first.
Complete the following to integrate PAM RADIUS Plug-in with IDaaS.
Step 1: Prepare
PAM RADIUS Plug-in for installationComplete the following to prepare PAM RADIUS Plug-in installation:
1. On each server that requires protection with second-factor authentication, install the PAM RADIUS software. See https://docs.fedoraproject.org/en-US/epel/ for Extra Packages for Enterprise Linux (EPEL).
2. Log in or substitute the user to the root user. The PAM RADIUS Plug-in requires root privileges.
3. Run the following commands for your operating system:
RHEL 9
sudo subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
RHEL 8
sudo codeready-builder-for-rhel-8-$(arch)-rpms
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
RHEL 7
sudo subscription-manager repos --enable rhel-*-optional-rpms \
--enable rhel-*-extras-rpms \
--enable rhel-ha-for-rhel-*-server-rpms
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Step 2: Install
PAM RADIUS Plug-inPerform the following on each server that requires protection with second-factor authentication:
1. Log in or substitute the user for the root user.
2. Install pam_radius as follows:
sudo yum install pam_radius
The RADIUS server configuration file is created at /etc/pam_radius.conf.
3. Add an Entrust Identity as a Service Gateway server to the configuration. To communicate with Entrust Identity as a Service Gateway, complete the following:
a. Enter the IP address or hostname and the port number.
Example: 123.145.10.10:1812
b. Enter the hostname or IP address (with port number) for an Identity as a Service Gateway.
Example: 10.10.10.10:1812
c. Enter the shared secret: secret. This should be the same shared secret you created for the Identity as a Service Enterprise Gateway. See Create and configure a Gateway for more information.
d. Enter the timeout value (in seconds) for the Identity as a Service Gateway. The timeout value is used by the module the PAM module waits for communication from an Identity as a Service Gateway.
– If the authenticator uses push authentication, a longer timeout is needed, for example, 30 or greater seconds.
– If the authenticator does not use push authentication, a shorter time is needed, for example, 10 seconds.
e. Run the following command to open the configuration file:
sudo vi /etc/pam_radius.conf
f. Add the following lines to the configuration file. Add the Identity as a Service Gateway IP and port, as follows:
# IP/FQDN [:port] shared_secret timeout(s)
gateway.domain.com:1812 secret 60
g. Save the changes by typing wq + Enter.
Step 3: Duplicate
a PAM RADIUS Plug-in configuration (if required)After the PAM RADIUS Plug-in is installed and configured on one system, you can duplicate the files for other servers from the first installation. These updated files can be deployed to any systems sharing the same version of the operating system.
1. Deploy the pam_radius package to required system.
2. From the first installation server, create a backup of the RADIUS server configuration file from Step 2: Install the PAM Plug-in and copy the package to common location so other servers can pick this file.
3. Create a backup of pam_radius.conf.
4. Copy file pam_radius.conf directory from the common location /etc and set access rights, as follows:
sudo chmod 600 /etc/pam_radius.conf
Choose the procedure for the applicable operating system.
● Configure
Red Hat Enterprise Linux 7 servers
After the PAM RADIUS Plug-in has been successfully installed and configured, you must modify the /etc/pam.d/sshd file.
Install second-factor authentication to SSH
1. Create a backup of /etc/pam.d/sshd.
The following example shows the contents of an unmodified file. These settings may be enabled on some systems depending on policy settings of the organization. Update them as required.
#%PAM-1.0
auth required pam_sepermit.so
auth substack password-auth
auth include postlogin
# Used with polkit to reauthorize users in remote sessions
-auth optional pam_reauthorize.so prepare
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session include password-auth
session include postlogin
# Used with polkit to reauthorize users in remote sessions
-session optional pam_reauthorize.so prepare
The modified file /etc/pam.d/sshd is as follows:
#%PAM-1.0
auth required pam_sepermit.so
auth required pam_radius_auth.so
auth substack password-auth
auth include postlogin
# Used with polkit to reauthorize users in remote sessions
-auth optional pam_reauthorize.so prepare
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session include password-auth
session include postlogin
# Used with polkit to reauthorize users in remote sessions
-session optional pam_reauthorize.so prepare
2. For one-step authentication, comment the line auth substack password-auth.
Changes made to the configuration file take effect immediately.
3. Configure the SSH daemon to be aware of challenge-response types of authentications, as follows:
a. Open the configuration file /etc/ssh/sshd_config.
b. Set the ChallengeResponseAuthentication and UsePAM flag to yes.
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication no
ChallengeResponseAuthentication yes
UsePAM yes
4. After making the configuration changes, enter the following to restart the sshd service:
sudo systemctl restart sshd
Note: Do not log out from the session used to configure the SSH PAM configuration. If you need to reverse the PAM changes, you can still do so from that terminal. It is very easy to lock up a system with a bad configuration.
● Configure
Red Hat Enterprise Linux 8 servers
After the PAM RADIUS Plug-in has been successfully installed and configured, you must modify the /etc/pam.d/sshd file.
Install second-factor authentication to SSH
1. Create a backup of /etc/pam.d/sshd.
The following example shows the contents of an unmodified file. These settings may be enabled on some systems depending on policy settings of the organization. Update them as required.
#%PAM-1.0
auth substack password-auth
auth include postlogin
account required pam_sepermit.so
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session optional pam_motd.so
session include password-auth
session include postlogin
The modified file /etc/pam.d/sshd is as follows:
#%PAM-1.0
auth substack password-auth
auth required pam_radius_auth.so
auth include postlogin
account required pam_sepermit.so
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the
user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session optional pam_motd.so
session include password-auth
session include postlogin
2. For one-step authentication, comment the line auth substack password-auth.
Changes made to the configuration file take effect immediately.
3. Configure the SSH daemon to be aware of challenge-response types of authentications, as follows:
a. Open the configuration file /etc/ssh/sshd_config.
b. Set the ChallengeResponseAuthentication and UsePAM flags to yes.
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication no
ChallengeResponseAuthentication yes
UsePAM yes
4. After making the configuration changes, enter the following to restart the sshd service:
sudo systemctl restart sshd
Note: Do not log out from the session used to configure the SSH PAM configuration. If you need to reverse the PAM changes, you can still do so from that terminal. It is very easy to lock up a system with a bad configuration.
● Configure
Red Hat Enterprise Linux 9 servers
After the PAM RADIUS Plug-in has been successfully installed and configured, you must modify the /etc/pam.d/sshd file.
Install second-factor authentication to SSH
1. Create a backup of /etc/pam.d/sshd.
The following example shows the contents of an unmodified file. These settings may be enabled on some systems depending on policy settings of the organization. Update them as required.
#%PAM-1.0
auth substack password-auth
auth include postlogin
account required pam_sepermit.so
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session optional pam_motd.so
session include password-auth
session include postlogin
The modified file /etc/pam.d/sshd is as follows:
#%PAM-1.0
auth substack password-auth
auth required pam_radius_auth.so
auth include postlogin
account required pam_sepermit.so
account required pam_nologin.so
account include password-auth
password include password-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the
user context
session required pam_selinux.so open env_params
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session optional pam_motd.so
session include password-auth
session include postlogin
2. For one-step authentication, comment the line auth substack password-auth.
Changes made to the configuration file take effect immediately.
3. Configure the SSH daemon to be aware of challenge-response types of authentications, as follows:
a. Open the configuration file /etc/ssh/sshd_config.
b. Set the ChallengeResponseAuthentication and UsePAM flags to yes.
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication no
ChallengeResponseAuthentication yes
UsePAM yes
4. After making the configuration changes, enter the following to restart the sshd service:
sudo systemctl restart sshd
Note: Do not log out from the session used to configure the SSH PAM configuration. If you need to reverse the PAM changes, you can still do so from that terminal. It is very easy to lock up a system with a bad configuration.
Step
5: Add PAM RADIUS Plug-in to Identity as a Service
Note: Entrust recommends that when multiple RADIUS applications are configured that each RADIUS application is given a unique shared secret.
Integrate a RADIUS client
1. Click
> Security > Applications. The Applications
page appears.
2. Click Add. The Select an Application Template page appears.
3. Under RADIUS and VPN Integrations, click PAM Plug-in. The Add PAM Plug-in page appears.
4. Optional: Edit the Application Name.
5. Optional. Enter a Description for your application.
6. Optional. Add a custom application logo as follows:
a. Click 
next
to Application Logo. The Upload
Logo dialog box appears.
b. Click 
to select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box displays your selected image.
d. If required, resize your image.
e. Click OK.
7. Click Next. The Setup page appears.
8. Click Add to next to Hosts to add the host name of the VPN server. The RADIUS agent receives the request on this host. The RADIUS Agent on the Gateway determines the RADIUS application the request is for based on the host name and port.
9. Enter the host name in the Host dialog box and then click OK. Repeat this step to add more host names.
10. In the Port field, enter the port on which the RADIUS agent accepts messages.
Tip: Do not enter 8443 as the port number for this application. Port 8443 is used by the Entrust Identity Enterprise agent in your Gateway.
Attention: The RADIUS agent
uses the host name that sent a request and the port number that it
received the request from to determine which RADIUS application made
the request. Because of that:
–Two RADIUS applications with the same port value cannot share any
host names.
–Two RADIUS applications that have one or more matching host names
must have different port values.
11. In the Shared Secret field, enter the shared secret that is used by your VPN server. This is the RADIUS secret shared between your VPN server and the RADIUS server. The shared secret value must match a shared secret in your RADIUS client.
12. From the Select RADIUS Agent drop-down list, select the name of the Gateway containing the RADIUS agent to which this application will be assigned.
13. Optional: From the Select RADIUS Attribute for IP Address drop-down list, select the RADIUS attribute that corresponds to your IP location.
14. In the Challenge Response Queue Max Time field, set the number of seconds that the RADIUS agent waits for a response to first-factor authentication. The default value is 180 seconds.
15. In the Challenge Response Queue Max Size field, set the maximum number of second-factor challenge requests allowed in the queue of your RADIUS application. The default value is 1000 requests. The maximum value is 10,000.
16. In the Request Cache Timeout field, set the number of seconds to cache requests. The default value is 10 seconds.
17. From the Character Set drop-down list, select the character set used to decode and encode string values (including the user ID and password values) in RADIUS messages. The options are UTF-8 and ISO-8859-1.
18. Optional: Select Log RADIUS messages to enable RADIUS message logging. When enabled, messages for the RADIUS agent are logged to the same log file as the gateway logs.
19. Optional:
Enable the Authentication Settings.
Select Enable Push Authentication Fallback if you want to authentication to fallback to another authenticator in the event of a failure. If required, set the Push Authentication Fallback Timeout to the number of minutes before the push authentication times out.
Select When authenticating the user will be asked to select their second-factor authenticator. When selected, after the user responds to the first-factor challenge, they are prompted to select their second-factor authenticator. The list of available second-factor authenticators is set by the resource rule.
The following is a list of supported strings matched to the authentication types:
Grid: grid
Knowledge-based Authentication: kba
One-time password: email, sms, voice
Smart Credential Push: scpush
Temporary Access Code: tac
Token: token
Token push: push
Select Indicate if requests must include the message-authenticator attribute for incoming messages to include the message-authenticator attribute for incoming messages.
Select Indicate if requests must include the message-authenticator attribute for outgoing messages to include the message-authenticator attribute for outgoing messages.
Select Remove domain from user ID for incoming requests to remove the domain value from the user ID during authentication when the user ID provided by the RADIUS client is in the format domain\username and the user ID in IDaaS is in the format username.
Select Indicate if Active Directory password authentication requests are handled by the same Gateway Instance that initiated the request to require that Active Directory password authentication and change requests that are initiated as part of the RADIUS authentication are handled by any Gateway Instance in the same Gateway cluster that initiated it. If disabled, the request is handled by any Gateway Instance.
Select Enable one-step multi-factor authentication. When enabled, the user enters their user ID and then their password and token response in the password field. If you select this option, second factor authenticators available in the resource rule are limited to token and temporary access code.
Enter the One-step multi-factor authentication security token length. This is the length of the token or temporary access code response if you enable one-step multi-factor authentication.
20. Optional.
Add Response Attributes. Response attributes are
returned to the RADIUS application after successful authentication.
Use this setting to configure RADIUS attributes to return information
such as the user's group information to the VPN server.
When adding response attributes, you optionally add group filters. For example:
Example:
Users in IDaaS may belong to one of the following groups CANADA,
US, UK, FRANCE.
The VPN server wants the FilterID attribute returned from the IDaaS
RADIUS agent to be the value NA or EUROPE, depending on whether
the user is in NA (Canada, US) or Europe (UK, France).
To do this, use a RADIUS attribute filter for the FilterID attribute
with a Groups value with the following filters:
- match CANADA, replace NA
- match US, replace NA
- match UK, replace EUROPE
- match FRANCE, replace EUROPE
Set the Response Attributes as follows:
Click
Add. The Add
a Response Attribute
dialog box appears.
Select the RADIUS Attribute ID from the drop-down list. The option you select depends on your VPN vendor.
Select the Value Type from the drop-down list.
To return a static value specific in the RADIUS attribute definition, select Static and enter a Value in the field and then click Add.
To return the user’s group membership, select Group and then optionally do the following:
Click Add to add filters.
Enter the Match and the Replace attribute filters.
Click Add to add more attribute filters.
If you add multiple filters, you can drag and drop them in order of preference.
Select Stop after matching filter if you only want one the filter to return one value. Using the example above, if you want NA to have preference over Europe, make sure to list Canada and US in the list of filters.
Multiple Values Per Attribute, enter the Value Separator and then click Add.
Note: If a user belongs to more
than one group, you can either add a separate attribute to your
RADIUS response for each group or you can combine all of the groups
into a single attribute. For example, if the user belongs to G1,G2,G3
then you would
- return a RADIUS response with three attributes
OR
- return a RADIUS response with one attribute and a value like
“G1,G2,G3” where the , is defined in the Value Separator setting
or a value like “G1 G2 G3” where the Value Separator is defined
as a space.
Attention: The default group separator is a space. If you have group names that are separated by a space, use another separator, such as a comma.
Repeat these steps to add more response attributes.
21. Optional: Configure the EAP Settings to set up the application to use the EAP RADIUS authentication protocol.
a. Select EAP Enabled to allow the RADIUS application to accept EAP messages.
– When enabled, authentication messages with EAP content are treated as EAP requests. The application can accept only EAP authentication requests.
– When disabled, incoming authentication requests are processed by the RADIUS application as a standard RADIUS authentication request (even if the request includes EAP content). In this case, the application can accept only standard RADIUS authentication requests.
b. Select the EAP Protocol from the drop-down list. The options are PEAPv0 with MS-CHAPv2 and PEAPv1 with GTC.
This setting defines the type of EAP authentication protocol that is performed on EAP requests received by the RADIUS application. Consult the configuration requirements of your VPN server to determine which EAP protocol to select.
c. Select Return MPPE Keys to include the MPPE (Microsoft Point-to-Point Encryption) recv and mppe send keys in the Access-Accept message returned during a successful EAP authentication. The setting is enabled by default.
d. Select Use PEAPv1 label when calculating MPPE Keys to use the PEAPv1 label when calculating the mmpe recv and mppe send keys.
e. Leave the Minimum TLS Version, Maximum TLS Version and Allow Weak Ciphers at the default settings unless you have an older VPN and need to configure these settings to allow older versions of TLS or weaker ciphers to interoperate with older VPN servers that do not support the latest versions.
22. Configure the Deprecated Settings if your RADIUS application is connected to a Gateway version older than 3.0. These values are only required for backwards compatibility.
a. Select Token OTP Only, Password with second-factor, or No first-factor as the Authentication Type. This setting defines the level of authentication required to access a RADIUS application that relies on a gateway RADIUS agent configured before release 3.1.
Note: MSCHAPv2 authentication is not supported when No first-factor authentication is configured for the RADIUS application.
23. Click Submit.
Step 6: Protect
PAM RADIUS Plug-in with a resource rule● Resource rules for RADIUS applications only include the Date / Time, Geolocation and Source IP Address condition restriction.
● The Authentication Decision steps that you can select for a RADIUS application resource rule depend on whether the RADIUS application uses EAP RADIUS authentication.
● If the settings of a RADIUS application on Identity as a Service are modified so that the application uses EAP RADIUS authentication, or the type of EAP protocol used is changed, the resource rule associated with the RADIUS application is automatically updated.
● RADIUS applications with no EAP support the following second-factor authenticators: knowledge-based authentication, temporary access code, one-time password, grid, hardware/software token, token push, and smart credential push.
● RADIUS applications with RADIUS MSCHAPv2 support only temporary access code and hardware/software token second-factor authenticators.
● When creating a resource rule for a RADIUS application, you can select EXTERNAL+no second-factor.
● RADIUS applications with RADIUS GTC support the following second-factor authenticators: software/hardware token, one time password, grid, temporary access code, knowledge-based authentication.
Create a resource rule to protect access to a RADIUS application
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
Attention: You must maintain the default of all groups if you want to allow external authentication and bypass second-factor authentication for users who do not already exist in Identity as a Service. External Authentication without second-factor is only available to low risk users of RADIUS applications that support External Authentication.
6. Click Next. The Authentication Conditions Settings page appears.
7. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
8. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
9. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
10. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
11. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
12. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
13. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
14. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
15. Define the Location History / Known Locations and Travel Velocity conditions.
The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
16. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
17. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
18. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
19. Click Submit to create the resource rule.
Step 7: Test
the integrationTest PAM RADIUS Plug-in for one-step authentication
Test the configuration by launching an SSH session from another server. Assuming the SSHD services are configured to use PAM RADIUS Plug-ins, the following example shows the beginning of an SSH login to the newly configured server.
1. Launch an SSHD session to the configured server.
2. Enter the username and password. Identity as a Service presents a second-factor authentication challenge.
3. Answer a valid challenge
4. User is logged in and shown the bash prompt.
5. Test PAM RADIUS Plug-in for one-step authentication
Test the configuration for two-step authentication
Test the configuration by launching an SSH session from another server. Assuming the SSHD services are configured to use PAM Plug-ins, the following example shows the beginning of an SSH login to the newly configured server.
1. Launch an SSHD session to the configured server.
2. Enter the username and password. Identity as a Service presents a second-factor authentication challenge.
3. Answer a valid challenge
4. The user is logged in and shown the bash prompt.
Consult the following for uninstall procedures and parameters to customize the installation.
● Uninstall
PAM RADIUS Plug-in
1. Go to /etc/pam.d/ and restore a backup of sshd.
2. Restore the backup file that you created in Step 4: Configure PAM applications to use IDaaS.
3. Remove the pam_radius package as follows:
sudo yum remove pam_radius
-or-
sudo yum erase pam_radius
4. After the uninstall, restart the sshd service, as follows:
sudo systemctl restart sshd
● PAM
RADIUS Plug-in parameters
The PAM RADIUS Plug-in has a few parameters that can be used to customize the installation.
See https://github.com/FreeRADIUS/pam_radius/blob/master/USAGE for more information.