docmain.css" /> Enable the Emulator for Automated Sign-on - Automated Sign-on for Mainframe Administrator Guide

3.5 Enable the Emulator for Automated Sign-on

The Initial Setup required in the emulator depends on which emulator and session type you are using. Follow the steps for your setup.

3.5.1 Reflection or InfoConnect Desktop - Workspace Automated Sign-on

The Workspace Automated Sign-on session type requires Reflection or InfoConnect Desktop version 16.2 or higher. This option enables the administrator to implement automated sign-on for users who create and save mainframe sessions on their desktops.

In brief, the Emulator administrator must:

♦ Configure Centralized Management

This global setting establishes a connection between the client and the MSS Administrative Server, which is needed to request and deliver the PassTicket for automated sign-on.

  1. In Reflection Desktop, open Reflection Workspace Settings.

  2. Click Configure Centralized Management.

  3. Check Enable Centralized Management.

  4. Enter the URL for your MSS Administrative Server (Management and Security Server).

    Click OK.

  5. Check Enable automated sign-on for mainframe sessions.

    This setting is needed to use Automated Sign-on for Mainframe when sessions are created by users and saved on their individual desktops. When enabled, the automated sign-on macro inserts a time-limited PassTicket to log the user on to the mainframe session.

♦ Create the automated sign-on macro and save the session document

  1. Gather these details for the macro:

    • the application ID

    • valid logon credentials for the mainframe application

  2. In Reflection Desktop, create a session and configure it to connect to the host that users will automatically log on to.

  3. From the Macros tab, click Record VBA.

  4. Log on to the mainframe host application with valid credentials, and then click Stop Recording.

  5. In the Recording Complete dialog, save the macro in the current document’s project. Name the macro according to these requirements:

    • To apply the macro to all sessions connecting to this mainframe, name it SignOn.

    • To apply this macro only to sessions connecting to a specific port on this mainframe, append the port number to the name. For example: SignOn_623.

    NOTE:If you want to specify different logon information for different ports on the same host, you can create a macro for each port and save these macros in the same VBA module.

    For example, if you connect to a mainframe on port 623 and on port 723 with a different logon, create different macros named SignOn_623 and SignOn_723. When the session connects, the port-specific macro is used.

  6. Save the session document file with the required name: ASM.rd3x.

  7. In the VBA Editor, open the ASM Project > Modules. Open the Recorded module.

  8. Edit the macro code to use PassTickets:

    1. Add this line after the variable declarations:

      ibmCurrentTerminal.GetDASOPassTicket("APPID")

      where "APPID" is replaced with the host application ID (noted in step 1).

    2. Replace your user name with the DASOUserID retrieved by the GetDASOPassTicket function:

      ibmCurrentScreen.SendKeys(ibmCurrentTerminal.DASOUserID)

      As a result, your DASOUserID will be sent instead of your user name.

    3. Comment out or delete the line that uses the PasswordBox function to prompt the user for the password.

      hiddenTextEntry = ibmCurrentTerminal.Macro.PasswordBox("", "")
      If (hiddenTextEntry = "") Then
          Err.Raise 5002, "Hidden TextEntry", "No Value Provided.", "VBAHelp.chm", "5002"
      End If
      
      ibmCurrentScreen.SendKeys(hiddenTextEntry)

    4. Replace that line with one that contains the DASOPassTicket that was retrieved by the GetDASOPassTicket function call, like this:

      ibmCurrentScreen.SendKeys(ibmCurrentTerminal.DASOPassTicket)

    HINT: To add another macro for a specific port on this mainframe, disconnect this session and connect on that port. Then repeat the steps in this procedure to record another SignOn macro and save it with the port number appended to the SignOn name (for example, SignOn_623).

  9. Save the macro. Close the VBA editor and save the session document.

The Initial Setup requirements are met for Workspace Automated Sign-on.

Next step: Configure the settings to run a Simple Test.

3.5.2 Reflection or InfoConnect Desktop - Managed Sessions

Automated Sign-on for Mainframe is available with Reflection or InfoConnect Desktop version 16.0 or higher.

In brief, the Emulator administrator must:

Note: The automated sign-on macro will be recorded and edited in the session that is created in Management and Security Server.

Enable Centralized Management

This global setting establishes a connection between the client and the MSS Administrative Server, which is needed to request and deliver the PassTicket for automated sign-on.

  1. In Reflection Desktop, open Reflection Workspace Settings.

  2. Click Configure Centralized Management.

  3. Check Enable Centralized Management.

  4. Enter the URL for your MSS Administrative Server (Management and Security Server).

    Click OK.

The Initial Setup requirements are met for Reflection/InfoConnect Desktop - Managed Sessions.

Next step: Configure the settings to run a Simple Test.

3.5.3 Reflection ZFE

Reflection ZFE uses Management and Security Server for centralized management, so this requirement is met.

Be sure these requirements are met:

When the Initial Setup requirements are met for Reflection ZFE, continue with the settings to run a Simple Test.

3.5.4 Reflection for the Web

Reflection for the Web uses Management and Security Server for centralized management, so this requirement is met.

Be sure these prerequisites are met:

When the Initial Setup requirements are met for Reflection for the Web, continue with the settings to run a Simple Test.

3.5.5 Rumba+ Desktop

Automated Sign-on for Mainframe is available with Rumba+ Desktop 9.4.1 (or higher).

Details are documented in the Rumba+ Desktop Administrator Guide > MSS Automated Sign-On.

In brief, the Rumba administrator must:

  • Ensure the Prerequisites are in place, including the Automated Sign-On for Mainframe activation file. To verify or install the activation file, see 1. Activate the Automated Sign-On for Mainframe Add-On

  • Create an automated sign-on connection macro

  • Create a session profile that contains the macro

After these Initial Setup tasks are completed, continue with the steps — in this guide — to configure Rumba+ Desktop, and then run a Simple Test.

Related topics