Configure APM to connect to Oracle with Enterprise User Security (EUS). How to resolve the error: java.sql.SQLException: unsupported verifier type

Document ID : KB000048175
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

A known issue has been identified by Oracle when clients such as the APM Enterprise Manager attempt to connect when Enterprise User Security (EUS) has been enabled.

EUS enables clients to connect to Oracle databases using LDAP authentication.

Details about EUS are available at the Oracle documentation site:

Details about Oracle Bug ID 8254139 for the EUS problem are available at the Oracle support site:

For Oracle JDBC driver version 11.2.0.1, the workaround is to use -Doracle.jdbc.thinLogonCapability=o3 as a JVM startup option.

  • Note that this property is ignored for Oracle JDBC driver version 11.2.0.3.

Problematic error logged during APMDB schema creation:

java.sql.SQLException: unsupported verifier type
       at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:647)
       at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:359)
       at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:531)
       at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:221)
       at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
       at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
       at java.sql.DriverManager.getConnection(Unknown Source)
       at java.sql.DriverManager.getConnection(Unknown Source)
       at com.wily.apm.dbutil.SqlExecutor.getConnection(SqlExecutor.java:98)
       at com.wily.apm.dbtools.createschema.CreateSchema.createSchema(CreateSchema.java:141)
       at com.wily.apm.dbtools.createschema.CreateSchema.main(CreateSchema.java:109)

Solution:

Depending upon how you invoke APM, one of the following changes must be made to set the required property:

  • If the Enterprise Manager is invoked as a command line application:

    File : Introscope_Enterprise_manager.lax
    location :<introscope install dir>
    Modification Required : Append "-Doracle.jdbc.thinLogonCapability=o3" to "lax.nl.java.option.additional"

  • If the Enterprise Manager is invoked as a service:

    File : EMservice.conf
    location :<introscope install dir>\bin
    Modification Required : Add a new parameter "wrapper.java.additional.<n>=-Doracle.jdbc.thinLogonCapability=o3".
    (where <n> is the next number in sequence) to the # Java Additional Parameters section.

  • For all Enterprise Managers invoked by either method:

    File:Tess-default.properties
    Location : <introscope install dir>/config
    Modification Required : Append "-Doracle.jdbc.thinLogonCapability=o3" to the jvm option for:
         Defect Aggregation (defects.jvmArgs)
         Stats Aggregation (dailystats.jvmArgs)