I then had to go in and update the configuration on the database to enable connection via the old SID style approach. Unfortunately, this failed as the wpsconfig script calls out to programs that expect the url to follow the old school syntax (the stack trace show an index-out-of-bounds exception while parsing connect srings).
I needed to run WPSConfig connect-database to update all the hidden bits of configuration around the portal installation. Changing the url to use the PORT/SERVICE_NAME approach looked to mostly work, but didn’t quite spread the changes to everywhere required. I tried this first as it felt familiar, but things didn't work.
The documentation for doing this suggested using the old school SID style of url. It seems the new preferred way of doing Oracle JDBC URLs discovered this information while working with making a WebSphere Portal instance use Oracle as it’s data repository. In particular Oracle 10G XE out of the box doesn’t support this sort of option.
Oracle JDBC driver except classes for NLS support in Oracle Object and Collection types. Implements JDBC 4.3 spec and certified with JDK11 and JDK17. However, the Oracle JDBC OCI driver support is the same as thick client support, in which all of Oracle Advanced Security features are implemented. Somewhere in the past couple of releases of Oracle this transparent mapping has ceased to exist. This applies to ojdbc8.jar, ojdbc11.jar, ucp.jar and ucp11.jar. The Oracle JDBC Thin driver does not support Oracle Advanced Security third party authentication features such as RADIUS, Kerberos, and SecurID. Java Developers have always smiled and nodded with this statement as the oracle thin client jdbc url would always be something would work because databases always either had the SID and SERVICE_NAME as the same, or there was some magic that the Oracle listeners did to make this work.
To obtain the ticket, you need to run the kinit command with the username.… or how to setup your Oracle XE database so that JDBC database urls will work like they traditionally have.įor many years Oracle has been telling everyone Oracle SID != SERVICE_NAME. Kerberos Authentication Overview at īefore configuring a data source, ensure that you have all the necessary prerequisites.įirst, you need to obtain a ticket for a user. The following documentation might help you:
Kerberos installed and configured on your Windows Server machine. Windows Server with configured Active Directory authentication. Make Someone Else do the Work - Managing Oracle Database 19c Users in Active Directory (part 1 - Kerberos) at Ĭonfiguring Kerberos Authentication at For more information about configuring and installing Kerberos, see the Kerberos documentation at .įor more information about configuring the server side, consider reading the following links. Client sideīefore configuring the connection in DataGrip, ensure that you have configured and got the following prerequisites:Ĭonfigured Kerberos client to run kinit. Consider reading the official documentation of these vendors. This tutorial does not cover the configuration of Windows Server and Oracle instances. Connect to Oracle by using Kerberos (JDBC Thin Driver) Prerequisites