How The Java Helper (JHO) Works and Registry Settings for Controlling the JHO Behaviour
(Doc ID 1140293.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Enterprise Single Sign-On Suite Plus - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
First a general overview about how the Oracle Enterprise Single Sign-On (eSSO) Logon Manager (LM) Java helper object (JHO) works:
- The LM agent will check if any java process is being started at the OS level.
- When it detects one, it will "inject" the ssojho.jar into the classpath.
- The com.passlogix.vgo.ho.Jho class will be instantiated and will register as an AWT event handler.
- Whenever an AWT event is generated in that JVM, the ssojho handler will be called.
- To interact with the ssoshell.exe, the JHO will open a hidden native window for every Java AWT window.
- If LM reacts to that hidden window, then the JHO will select the username and password from there and inject them in the java controls.
- To do this it has to use the Java Native Interface (to open the hidden native shadow windows), and this is done in ssojho.dll.
The Java Helper Object registry settings described in this article allow you to specify which events eSSO Logon Manager agent should recognize when responding to a Java application. Modify these settings to troubleshoot and optimize eSSO LM performance when responding to Java applications.
These settings have been introduced in and are present in all releases subsequent to the following releases of eSSO LM:
- eSSO LM version 10.1.4.0.3 Fixpack 12
- eSSO LM version 10.1.4.0.4 Fixpack 6
- eSSO LM version 10.1.4.0.5 Fixpack 3
- eSSO LM version 10.1.4.1
- eSSO LM version 18.104.22.168.0
- eSSO LM version 22.214.171.124.0
- eSSO LM version 126.96.36.199.0
- eSSO LM version 11.1.2.x
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document