12.3 Other Tasks Following Installation

After the initial installation or upgrade of Platform Services, other tasks that you may need to perform from time to time include the following:

12.3.1 Configuring PAM

If you have chosen to configure for authentication redirection on a platform that is running Linux or UNIX, you will need to manually configure PAM on that system. For technical instructions on how to configure PAM for authentication, see PAM Configuration Notes.

The Platform Services installer automatically copies sample configurations you can use as templates to the following location:

  • If you are running Linux: /usr/local/ASAM/PlatformServices/pam.d/

  • If you are running UNIX: /usr/local/ASAM/PlatformServices/pam.conf.sample/

12.3.2 Configuring LAM on AIX

If you have chosen to configure for authentication redirection on a platform that is running AIX, and you want to use IBM’s proprietary Loadable Authentication Module (LAM), you will need to manually configure the Fan-Out Driver’s LAM module on that AIX system. For technical instructions on how to configure LAM for authentication, see LAM Configuration Notes.

The Platform Services installer automatically copies sample LAM-related configuration files you can use as templates to the following location:

  /usr/local/ASAM/bin/PlatformServices/methods.cfg.sample
  /usr/local/ASAM/bin/PlatformServices/user.sample
  /usr/local/ASAM/bin/PlatformServices/user.sample2

12.3.3 Running a Full Synchronization

Upon initial deployment of the Fan-Out Driver Platform Services, you may find it useful and necessary to perform an initial migration or synchronization of users and groups within the Identity Vault. You can perform a full synchronization by executing asamrcvrd fullsync. Location of this executable will vary depending on your target platform. See Table 12-3 for the appropriate full command line that includes your directory location.

Table 12-3 Command for Full Synchronization by Platform

Platform

Synchronization Command

Linux

/etc/init.d/asamrcvrd fullsync

Solaris

/etc/init.d/asamrcvrd fullsync

AIX

/etc/rc.d/init.d/asamrcvrd fullsync

HP-UX

/sbin/init.d/asamrcvrd fullsync

12.3.4 Starting Platform Services

Starting Platform Services requires you to start one or more of the following components, depending on your configuration:

  • Platform Receiver

  • Platform Services Process

  • Platform Services Cache Daemon

For more information about these components, see About Platform Services for Linux and UNIX and Section 13.0, Configuring and Administering Platform Services.

Starting the Platform Receiver

You can start the Platform Receiver by executing asamrcvrd start. Location of this executable will vary depending on your target platform. See Table 12-4 for the appropriate full command line that includes your directory location.

Table 12-4 Command for Starting the Platform Receiver

Platform

Platform Receiver Start Command

Linux

systemctl start asamrcvr

Solaris

/etc/init.d/asamrcvrd start

AIX

/etc/rc.d/init.d/asamrcvrd start

HP-UX

/sbin/init.d/asamrcvrd start

Starting the Platform Services Process

You can start the Platform Services Process by executing asampspd start. Location of this executable will vary depending on your target platform. See Table 12-5 for the appropriate full command line that includes your directory location.

Table 12-5 Command for Starting the Platform Services Process

Platform

Platform Services Process Start Command

Linux

systemctl start asampsp

Solaris

/etc/init.d/asampspd start

AIX

/etc/rc.d/init.d/asampspd start

HP-UX

/sbin/init.d/asampspd start

Starting the Platform Services Cache Daemon

You can start the Platform Services Cache Daemon by executing asampsd start. Location of this executable will vary depending on your target platform. See Table 12-6 for the appropriate full command line that includes your directory location.

Table 12-6 Command for Starting the Platform Services Cache Daemon

Platform

Platform Services Cache Daemon Start Command

Linux

systemctl start asamps

Solaris

/etc/init.d/asampsd start

AIX

/etc/rc.d/init.d/asampsd start

HP-UX

/sbin/init.d/asampsd start

12.3.5 Stopping Platform Services

Stopping Platform Services requires you to stop one or more of the following components, depending on your configuration:

  • Platform Receiver

  • Platform Services Process

  • Platform Services Cache Daemon

For more information about these components, see About Platform Services for Linux and UNIX and Section 13.0, Configuring and Administering Platform Services.

Stopping the Platform Receiver

You can stop the Platform Receiver by executing asamrcvrd stop. Location of this executable will vary depending on your target platform. See Table 12-7 for the appropriate full command line that includes your directory location.

Table 12-7 Command for Stopping the Platform Receiver

Platform

Platform Receiver Stop Command

Linux

systemctl stop asamrcvr

Solaris

/etc/init.d/asamrcvrd stop

AIX

/etc/rc.d/init.d/asamrcvrd stop

HP-UX

/sbin/init.d/asamrcvrd stop

Stopping the Platform Services Process

You can stop the Platform Services Process by executing asampspd stop. Location of this executable will vary depending on your target platform. See Table 12-8 for the appropriate full command line that includes your directory location.

Table 12-8 Command for Stopping the Platform Services Process

Platform

Platform Services Process Stop Command

Linux

systemctl stop asampsp

Solaris

/etc/init.d/asampspd stop

AIX

/etc/rc.d/init.d/asampspd stop

HP-UX

/sbin/init.d/asampspd stop

Stopping the Platform Services Cache Daemon

You can stop the Platform Services Cache Daemon by executing asampsd stop. Location of this executable will vary depending on your target platform. See Table 12-9 for the appropriate full command line that includes your directory location.

Table 12-9 Command for Stopping the Platform Services Cache Daemon

Platform

Platform Services Cache Daemon Stop Command

Linux

systemctl stop asamps

Solaris

/etc/init.d/asampsd stop

AIX

/etc/rc.d/init.d/asampsd stop

HP-UX

/sbin/init.d/asampsd stop

12.3.6 Testing Platform Services for PAM or LAM

If you are using PAM (or LAM on AIX) for password authentication, it may be helpful to verify that the Platform Services Process (asampsp) and the API Library (libascauth) are functioning properly, before you finalize PAM configuration. You can do this with a program called asctest, which is included with your Platform Services installation. Here’s where to find it:

/usr/local/ASAM/bin/PlatformServices/PlatformClient/asctest

This program allows you to test the various calls (listed in Table 12-10) that can be made to the API library in support of PAM. To use asctest, simply enter it from a command line with no parameters. When prompted select the desired method by entering its corresponding letter (a-o) and respond to any further prompts. The following table provides descriptions of the API methods.

Table 12-10 API methods used for PAM.

API Method

Description

ASC_ADMINRSTPASSWD

Reset a user password using an administrative reset.

ASC_CHGPASSWD

Change a user’s password.

ASC_CHKPASSWD

Check a user’s password.

ASC_DAYS

Convert seconds to days.

ASC_GETCONTEXT

Look up a user’s context from a contextless name.

ASC_GETGROUPBYGID

Look up a group by its gidNumber.

ASC_GETUSERBYUID

Look up a user by its uidNumber.

ASC_GRPMEM

List a group’s members.

ASC_LISTSEQV

List a user’s security equivalences.

ASC_READATTR

Read a single-valued attribute on a user.

ASC_READGROUPATTR

Read an attribute on a group.

ASC_RIGHTS

Test attribute rights for one object over another.

ASC_SECEQUAL

Check user security equivalence to another object.

ASC_STRERROR

Convert ASCLIENT error code into a human-readable text string.

ASC_USER_INCLUDE_EXCLUDE

Check whether a user matches the include/exclude list.