Activating Console Changes Causes OCCAS to Throw a "User authentication failed" Exception When TimesTen Database is Used as JDBC Datasource
Last updated on DECEMBER 20, 2017
Applies to:Oracle Communications Converged Application Server - Version 5.0.0 and later
Information in this document applies to any platform.
Oracle Communications Converged Application Server (OCCAS) is configured to run with an Oracle TimesTen database with following setup:
- TimesTen caches database tables
- TimesTen installation is co-located with OCCAS engines
- TimesTen direct connection is used
In the OCCAS Administration Console (Domain -> Services -> Data Sources -> New -> Create a New JDBC Data Source) the Java Database Connectivity (JDBC) datasource is configured with the following test values:
- jndi -> test
- URL -> jdbc:timesten:direct:tester
- Driver class -> com.timesten.jdbc.TimesTenDriver
- hostname -> localhost
- port -> 0
- username -> xxxx
- password -> xxxx
Refer to http://download.oracle.com/otn_hosted_doc/timesten/1121/quickstart/html/admin/j2ee_weblogic.html for more information on setting up TimesTen in WebLogic Server (WLS).
When Activate Changes is clicked the following "User authentication failed" exception occurs (in engine log also):
However, testing the configuration during the Create a New JDBC datasource process results in a successful connection.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms