Chat now with support
Chat with Support

Enterprise Single Sign-On 8.0.6 - SSOWatch Administrator Guide

1 Overview 2 SSOWatch 3 Configuration Editor: Enterprise SSO Studio
3.1 Interface Overview 3.2 Starting and Stopping Enterprise SSO Studio 3.3 Creating or Opening a Configuration 3.4 Configuring General SSO Parameters 3.5 Defining PFCP and Application Profiles 3.6 Defining Application and Technical Definition Objects 3.7 Defining Window Objects 3.8 Testing the SSO 3.9 Exporting or Importing Objects 3.10 Managing Objects in the Tree 3.11 Saving Object Configurations 3.12 Managing Configuration Updates 3.13 Refreshing the Tree
4 The Generic Plug-in 5 The Microsoft Internet Explorer Plugin  6 The SAP R/3 Plug-in 7 Terminal Type Applications 8 The HLLAPI Plug-in 9 Advanced Configuration 10 OLE/Automation Interface Appendix A: Cache Tuning and Asynchronous Update of the Application Data Appendix B: Integrating Care-FX with SSOWatch

9.1.1.1 Scripting Logic

Actions are executed one after the other. Their execution is based on a True or False state, which is transmitted to each action, and sometimes modified by some of them. An action is executed only if its state (Condition) corresponds to the current state, or if no state is specified for this action (No condition).
The initial state of an action is True.
The following table summarizes the behaviors by indicating whether an action is performed on the basis of its execution condition and the current state. The symbol "" means that the action is performed.
State Condition
True
False
None
 True
 
 False
 
This logic allows you to manage simple actions of the If…Then…Else… type.

9.1.1.2 Data "Buffer"

All the actions include a context that contains the following data:
•
The current state: this can be modified by any action, thus affecting the execution of the next actions.
•
The Handle of the currently processed window.
•
A memory Buffer allowing data to be passed between actions.
•
The identifier of the connected application user.
•
The associated password.
•
The value of the last recovered SSO parameter (other than the identifier and the password).
•
The account associated with the application in the security database.
•
A pointer to custom user data.
The context data is maintained in a data buffer that is initialized before each Script execution in the following way:
•
The current state is set to True.
•
The window Handle is initialized with the handle of the currently processed window.
•
The memory buffer is empty.
•
The identifier, password, and service name are initialized with current values. If the window has the value "Bad password", the user is requested to provide the correct password during this step.
•
The pointer to custom user data is set to NULL.

9.1.2 The Actions Tab

By default, the Actions tabbed page is empty. The following figure shows an example of a filled in Actions tabbed page.
The list of actions to be performed is displayed in a read only state, and a check box allows you to specify whether or not this window manages bad passwords. To build or edit a script, you must use the Script Editor.

9.1.3 Script Editor

The Script Editor window is made up of four parts:
•
A toolbar.
•
An actions list.
•
A dynamic panel allowing you to edit selected action parameters.
•
The OK and Cancel buttons.
The actions list has three columns:
•
The actions.
•
The execution condition (or state).
•
The actions parameters.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating