Kerberos Authentication Using SQL Developer Is Not Working with Thin driver In AWS Workspace
(Doc ID 2979860.1)
Last updated on OCTOBER 12, 2023
Applies to:
Oracle SQL Developer - Version 22.2.1 and laterInformation in this document applies to any platform.
Symptoms
On : 22.2.1, 23.1 versions, Making and Saving Connections
SQL Developer is not working for Kerberos authentication with Thin driver when installed in AWS Workspace environment. It fails with following error:
ERROR:
Status: Failure - Test failed: IO Error: The service in process is not supported. No valid credentials provided (Mechanism level: Message stream modified (41))(CONNECTION_ID= xxxxxxx)
However, OCI Thick driver works.
SUMMARY:
SQL Developer from laptop: OCI Thick works, Thin works
SQL Developer from AWS: OCI Thick works, Thin fails with above error.
Sample Working environment
SQL Developer 23.x on Windows Desktop
Kerberos works fine for Instant client (OCI drivers) as well as with JDBC thin drivers.
Sample Non-working environment
Amazon (AWS) desktop (VDI) having Windows environment.
Kerberos works for Instant client (OCI drivers), but fails for JDBC Thin drivers.
WHAT ELSE WORKS:
You are able to connect with SQL* Plus in AWS Workspace.
It works with both SQL Developer 22.1 and 23.1 on laptops with same configuration.
Without username and password, it works with Thick drivers, but not with Thin drivers in AWS Workspace.
WORKAROUND:
The workaround is to use OCI Thick driver:
How To Integrate the Oracle Client and OCI Thick Drivers with SQL Developer (Document ID 2121278.1)
Changes
Using AWS Workspace.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |