Skip to main content

Hubble Connection Protocol

Below is the sequence for a Hubble user to connect from a client machine to the Oracle database.

  1. Hubble connects to EBS data stored in the Oracle DB using the JDBC Thin Driver from Oracle Corporation. The Oracle JDBC Thin Driver implements the Oracle O3LOGON challenge-response protocol to authenticate the user.

  2. The connection to the EBS database is made using a system account setup in Administrator, which is controlled by your own IT department. It is set up so that end users do not need any details about it. It is the responsibility of the customer to set the policy for and to control access to our Administrator application.

  3. The Hubble User ID is the same as the EBS User ID. However, because Oracle has encrypted the EBS password, Hubble has its own application passwords.

  4. The Hubble password is encrypted within our own application and the generated hash is compared to the hash stored in the Object Repository at login time.

  5. When a Hubble user logs in to our application, only the encrypted hash is transmitted. If it matches the hash in the Object Repository, then the user can login.

  6. Next, the Hubble application queries EBS to find the user’s list of Responsibilities. The user is asked to select a Responsibility from this list. The data security rules for the chosen EBS Responsibility will affect the SQL statements that the Hubble application sends to the EBS database server whenever a query is executed.

  7. At no time is a password sent from the Hubble application to the Hubble Object Repository or to EBS in an unencrypted form.

    More information on the Oracle 03 Login Challenge Response can be found at: http://docs.oracle.com/cd/B19306_01/java.102/b14355/clntsec.htm