-
1. Re: SQLcl and integrated Windows authentication
Gaz in Oz Nov 7, 2018 9:36 AM (in response to hwsbry)Please read these two threads,.
What is the purpose of the "SET WALLET" parameter?
and
Re: sqlcl mkstore and tns question
For example:
F:\>sql /@jdbc:oracle:oci8:@mydb
-
2. Re: SQLcl and integrated Windows authentication
hwsbry Nov 9, 2018 6:57 PM (in response to Gaz in Oz)Thanks, I'll take a look and see if that helps out.
-
3. Re: SQLcl and integrated Windows authentication
Gaz in Oz Nov 12, 2018 10:05 AM (in response to hwsbry)hwsbry wrote:
Is it possible to configure SQLcl to use integrated Windows authentication?
Ihave some DBs with everything configured properly and I can login with sqlplus with the following
Re-reading this, it would be very helpful if you supplied answers to the following:
. What do you actually mean by "integrated Windows authentication"?
. How have you configured the users? Please show your setup of a user.
. What Oracle documentation, specificallly, did you follow to get "everything configured properly"?
. What is your database version, to 4 significant digits ("select * from v$version;")?
. What is the output of:
> sql -verbose /@<TNS_ENTRY>
The error you are getting looks like it is due to sqlcl not being able to find the Oracle OCI libraries required for OS authentication.
Make sure OCI libraries are accessible from sqlcl.
-
4. Re: SQLcl and integrated Windows authentication
hwsbry Dec 17, 2018 10:35 PM (in response to Gaz in Oz)Thanks for trying to help out Gaz. I'll just say that it turned out that the issue lay with my command line of choice and not any of my configurations. I'm currently using MobaXterm for pretty much all of my command line interactions and it turned out that my issue lay in the fact that the session I built for SQLcl did not retain the Windows PATH environment. I will try to answer your questions in case something similar occurs for other users though.
- To me, integrated Windows authentication, IWA, means that I can pass my Windows login to the Oracle database and be authenticated.
- User is configured
- create user "USERNAME@DOMAIN.COM" identified externally;
- grant create session to "USERNAME@DOMAIN.COM";
- Used the Oracle 12.2 DB security guide. Specifically the section for configuring Kerberos authentication.
- 12.2.0.1
- I won't go into the verbose output as everything is working.
Thanks again for your help and I think your final consensus that the OCI libraries is supported by the fact that I do indeed have a traditional client install with the bin in my PATH and once I configured MobaXterm to pay attention to that everything works as expected.