*REGFAC authentication method

The primary purpose of the *REGFAC authentication method is to facilitate additional authentication requirements.

*REGFAC authentication method will call the exit program registered under exit point QIBM_QSY_AUTH during authentication processing. Refer to Additional Authentication Exit Program. The exit program is called after a successful authentication. It is not called if the authentication fails.

The exit program has sole responsibility for doing the additional authentication. If authentication is not performed by the exit program and *REGFAC is the only authentication method, this does not result in MFA protection. The administrator should take great care in monitoring the validity of the registered exit program.

Traditionally authentication is thought of as verifying a password. This exit program will be called for more cases. For instance, when the password is a special value.

Authentications using Kerberos and SSH, which do not require a password or TOTP value, will indirectly call the exit program via the interface used to associate a user profile with the Kerberos or SSH authentication.

The operating system gives the exit program information associated with the authentication. The exit program then has the ability to verify the information and return a value to the operating system that causes the authentication to pass or fail.

The *REGFAC authentication method can be used along with the *TOTP authentication method or it can be used independently. If used independently, the value entered into the additional factor field will be passed to the exit program. It can be used by the exit program to perform additional verification. If used along with the *TOTP authentication method, the additional factor field passed to the exit program will be blank.

The exit program is called for these actions:
  • Sign-on
  • Get Profile Handle API calls
    • The Set Profile Handle API calls use the profile handle. However, the authentication only happens on the get call. If the exit program allows the handle to be created, then the set using it will be allowed.
  • Generate Profile Token API calls
    • The Set to Profile Token API calls use the profile token. However, the authentication happens on the generate call. If the exit program allows the token to be created, then the set using the token is allowed provided the enhanced profile token information matches on the generate and set.
  • NetServer remote file access
Table 1. Interfaces with additional information parameters
Original API API with additional information parameters
QSYGETPH QSYGETPH, with all optional parameters
QsyGetProfileHandle QsyGetProfileHandle2
QsyGetProfileHandleNoPwd QsyGetProfileHandleNoPwd2
QSYGENPT QSYGENPT, with all optional parameters
QsyGenPrfTkn QsyGenPrfTkn2
QsyGenPrfTknE QsyGenPrfTknE2