Single SignOn Installation This page explains how to set up Single SignOn so that users enter their LAN Manager passwords to log on to OpenVMS. Pre-Requisites You are going to need the following: OpenVMS V7.1 installed and running. FT1 (BL5) or later is required (this is X67V or later on Alpha and X6FL or later on VAX). MOTIF V1.2-4 (for support of the new /LOCAL qualifier, V1.2-3 will work just fine in all other respects). PATHWORKS 5.0d. Installed, configured (can be primary domain controller, backup (secondary) domain controller, or member), and running in a LAN Manager domain. PATHWORKS authentication module. This will ship on the PATHWORKS kit. For now you copy a field test version; select either vax or alpha. What To Do Here's what you need to do to get External Authentication running on your system. Rename the PATHWORKS authentication module that you copied so its named PWV5_ACME.EXE. Place it in SYS$LIBRARY, and make sure it is world readable. Edit your system startup file and add the following commands so they are executed after PATHWORKS is up and running (to save yourself a reboot execute these three commands now as well): $!+ $! Turn on Single Signon, using PATHWORKS as the authenticator. $!- $ define /system /exec SYS$ACME_MODULE SYS$LIBRARY:PWV5_ACME $ install add /open /head /share sys$acme_module $ define /system /exec SYS$SINGLE_SIGNON 1 Enable external authentication on a per-user basis. For each user: Use the PATHWORKS ADMIN utility to set the HOSTNAME field in the user's LAN Manager domain account to his/her OpenVMS account name. Note that this step is only necessary if the user's LAN Manager userid is not the same as their OpenVMS username. Tell OpenVMS that this user is to be externally authenticated: $ mcr authorize UAF> MODIFY user /FLAG=EXTAUTH UAF> EXIT $ That's it. Each user with the ExtAuth flag set will now have to specify their LAN Manager userid and password when logging in to the OpenVMS system. Last Updated: 2 April 1996