This section assumes that you have created an nssoApplication object. See Creating an nssoApplication Object. For v-GO to uniquely identify and respond to each logon, you must enter a unique name for the mainframe application. Also include all the necessary parameters.
Select the object's Single Sign-on tab > click General > enter a description.
The following figure illustrates a General page for a mainframe nssoApplication object.
Launch a terminal emulator session and the mainframe application so that you can reference the logon screen in the subsequent steps.
In ConsoleOne, right-click the nssoApplication object > select Properties > Single Sign-on > Application Type.
Click the Application Type drop-down list > Terminal Emulator Logon (Manual Entry).
(Optional) Use v-GO to fill in some information.
v-GO can save you time by entering some information for you in a Terminal Emulator Logon (Manual Entry) screen.
Click the Application Type drop-down list > Terminal Emulator Logon > Apply > Terminal Emulator Logon (Manual Entry).
Enter logon information in the Terminal Emulator Logon (Manual Entry) text box.
The following figure illustrates parameters in this text box.
You declare a data element by using a key-value pair. The key is the name of the configuration option and is either a reserved word such as IDField or a reserved word plus an integer, such as Field1 or Field2, when there can be more than one value for an option. The integers must be consecutive. You cannot skip or repeat numbers.
The value is the specific setting of a key for a particular logon configuration. The syntax for section names, key-value pairs, and other INI file settings are generally case sensitive.
For additional details, see Key-Value Pairs for Mainframe Logons.
To enable v-GO to change passwords for mainframe applications, enter information in the Terminal Emulator Logon (Manual Entry) text box. Identify the mainframe applications and configure mainframe pages.
You identify section pointers to subsections. After you enter information in the text box and click Apply, the NSSO system saves the information to a [*Mainframe] section in the ENTLIST.INI file
You enter a section used to configure a mainframe application. If multiple screens are expected for a mainframe applications, you set up pointers to the authentication screens (pages). If only one screen is expected, all settings and configurations can reside within this configuration setting.
The following table illustrates a section used to configure a mainframe application.
Subsections are identifiers for all authentication screens for a given mainframe application and section. Subsections enable v-GO to be flexible in mainframe sessions that have multiple applications.
The following tables illustrate a mainframe application that contains two different logon screens. The tables describe the process for obtaining values for keys that are derived from internal application settings such as IDField and PassField.
The following illustrates information in a Manual Entry text box.
[*Mainframe]
Section1=MainframeApp1
Section2=MultipleMainframeApp
[~MainframeApp1]
AllowReveal=1
Field1=1,2,ClCS Signon
Field2=2,11,Password
IdField=6,24
PassField=7,24
NovEnhancedProtection=0
[~MultipleMainframeApp]
Page1=MultipleMainframeApp Page1
Page2=MultipleMainframeApp Page2
[~MultipleMainframeApp Page1]
Field1=1,25,The Company Logo
Field2=18,22,Password
IDField=18,11
PassField=18,32
[~MultipleMainframeApp Page2]
Field1=5,25,P A S S W O R D
PassField=8,55
NewPWField=11,55
NewPWField=13,55
Save the updated property values by closing the object.
To save and exit, click OK. To save and continue making changes, click Apply.
This step regenerates the v-GO configuration data attribute. (This attribute contains data that v-GO needs from the individual application and password policy objects within the nssoSingleSignon container.)
You can also select the nssoSingleSignon object > click the v-GO tab > General > Generate.