unsupported verifier type

[Marco Droll]

Hi!

When using dotConnect 7.3 professional i'm encountering the "unsupported verifier type" exception when using special characters like "@" or "." in the connection string?!

here my code example:

Code: Select all

string cs = "user id=test@test;password=test;server=myServer.mydomain.de;Sid=mySid;
             home=oraclient11g_home1_32bit;direct=true;persist security info=True";

string selectUserQuery = "select user from dual";
OracleConnection myConnection = new OracleConnection(cs);
OracleCommand myCommand = new OracleCommand(selectUserQuery, myConnection);
myConnection.Open();

with regards
Marco Droll

[Shalex]

We have reproduced ORA-01017 when the user id connection string parameter contains "@" or ".". We will investigate the issue and notify you about the results.

Please specify the exact version of your Oracle server.

[Marco Droll]

The exact version of our oracle server is "Oracle Database 11g Enterprise Edition Release 11.2.0.3.0"

thx in advance for your efforts

with regards

Marco Droll

[Marco Droll]

Any news on this issue?

We are still stuck with version 6.3 due to using OID user verification with usernames like [email protected]. The database itself accepts them but dotConnect wont.

With regards
Marco Droll

[Shalex]

We are working on the problem. We will post here when the issue is fixed.

[Shalex]

The bug with generating ORA-01017 when the user id connection string parameter contains "@" or "." is fixed. We will post here when the corresponding build of dotConnect for Oracle is available for download.

[Shalex]

New build of dotConnect for Oracle 7.5.179 is available!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=1&t=25833.

[Marco Droll]

We are still experiencing the same problem with connection string containing special characters like @ or ".".

[Shalex]

Please run your program in the debug mode, set a break point in the code, navigate to Visual Studio > Debug > Windows > Modules and make sure that the Devart.* assemblies from the latest (7.5.179) version of dotConnect for Oracle are loaded in the process of your application:
Devart.Data.dll v 5.0.638.0
Devart.Data.Oracle.dll v 7.5.179.0

If this is so, please specify the exact text of the current exception and its stack trace.

[Marco Droll]

Update:

We now recognized that the error occurs due to using Oracle Internet Directory (OID) verified users. While in dotConnect 6.3 connecting to the database with an OID-user was unproblematic in all newer versions it throws the "unsupported verifier type"-exception.

The exception:
Message: NET: Unsupported verifier type
StackTrace:
bei Devart.Data.Oracle.cz.a(Encoding A_0, String A_1, String A_2, UInt32 A_3, Byte[] A_4, Byte[] A_5, Byte[]& A_6)
bei Devart.Data.Oracle.a7.a(Boolean A_0)
bei Devart.Data.Oracle.a7.b()
bei Devart.Data.Oracle.c6.a(b5 A_0, o A_1)
bei Devart.Data.Oracle.OracleInternalConnection..ctor(b5 connectionOptions, OracleInternalConnection proxyConnection)
bei Devart.Data.Oracle.an.a(p A_0, Object A_1, DbConnectionBase A_2)
bei Devart.Common.DbConnectionFactory.a(DbConnectionPool A_0, p A_1, DbConnectionBase A_2)
bei Devart.Common.DbConnectionPoolGroup.a(DbConnectionPool A_0, DbConnectionBase A_1)
bei Devart.Common.DbConnectionPool.a(DbConnectionBase A_0)
bei Devart.Common.DbConnectionPool.GetObject(DbConnectionBase owningConnection)
bei Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)
bei Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
bei Devart.Common.DbConnectionBase.Open()
bei Devart.Data.Oracle.OracleConnection.Open()
bei FoemiCore.Dialoge.LoginDialog.Login(String userName, String password)

This error also occurs with user names without any special characters.
Can you please have a look a this issue or do you have any hints for a workaround.

With kind regards

Marco Droll

[Pinturiccio]

dotConnect for Oracle doesn't support Oracle Internet Directory. We will investigate the possibility of implementing the Oracle Internet Directory support but there is no timeframe.

[Marco Droll]

Alright, but one further question.

Why does it work with version 6.3 and no longer in newer versions.
In my opinion the database gets the login credentials and verifies them with OID, so actually this shouldn't have anything to do with dotconnect?! Am I wrong?!

Any ideas to get it working anyway, any workaround?

Thanks and with great regards

Marco Droll

[Shalex]

We are investigating the question. We will notify you about the result as soon as possible.

[Danny Nieruch]

Hi,

are there any new results on this topic?
I came across the same problem.

I am evaluating the latest "dotConnect for Oracle 8.4 Professional Trial" and I am trying to establish a connection to a database through an OID user.

Code: Select all

            string connectionString = @"Server=xxx;
                                        Sid=xxx;
                                        Persist Security Info=True;
                                        Direct=True;
                                        user id=xxx;
                                        password=xxx";
            OracleConnection oracleCon = new OracleConnection(connectionString);
            oracleCon.Open();

But I am getting the same OracleException: NET: Unsupported verifier type
Stacktrace: at Devart.Data.Oracle.db.a(Encoding A_0, String A_1, String A_2, UInt32 A_3, Byte[] A_4, Byte[] A_5, Byte[]& A_6)

Why does it work with version 6.3 and no longer in newer versions.
In my opinion the database gets the login credentials and verifies them with OID, so actually this shouldn't have anything to do with dotconnect?! Am I wrong?!

That's what I thought too.

[Pinturiccio]

Hi,

Why does it work with version 6.3 and no longer in newer versions.
In my opinion the database gets the login credentials and verifies them with OID, so actually this shouldn't have anything to do with dotconnect?! Am I wrong?!

That's what I thought too.

dotConnect for Oracle sends credentials, and we don't know why the connection with OID isn't established. We are investigating the issue, but we can't tell any timeframe at the moment.

If you give us remote access to your OID, it would speed up our investigation.