Devart Forums

Edward Hollingsworth wrote:Our developers work for a large, well-known corporation and it's a shame that after believing faithfully in this control from a well-known company after all these years, a product would be put out to the public that totally breaks everything that has worked for many years.

Thank you!

Same feelings... I am using the dotConnect components for 8 years, and in my experience the support gradually becomes worse.

SOLVED! Devart, take note. I'm not seeing in the history for any information on this update to let us know.

The version 9.2.220 requires you to use case sensitive logins! If you run "select username, password_versions from dba_users", it MUST return at least 10G and 11G. The flag SEC_CASE_SENSITIVE_LOGIN must be set to 'True'. So say we were using a password of 'test', we reset the password to itself, 'test' and everything was working.

So do I win the trip to Hawaii?

PS version 9.3.230 is now out, mostly to support VS 2017.

Thanks!

In my case
returns As per company security policies, sec_case_sensitive_logon has been enabled in all databases.
My password is/was already case-sensitive, the username was provided in a lowercase (if it matters).

Any ideas?

Tried both uppercased and loweredcased user id - no luck

As stated: it MUST return at least 10G and 11G. It appears some modification are needed. Try resetting the existing password to the same one. If the username's password is "test", simply reset it to "test". That should cover it.

We are using x64 version of Oracle 11G.

Good luck. PS: I wont be responding to this thread any more.

Edward Hollingsworth wrote:As stated: it MUST return at least 10G and 11G

Oh, I see - thought it MUST return either 10G or 11G

Confirming for devArt: after resetting the password to the same value (we can afford to do this in DEV environment) the returns
After such changes, the connection became possible again.
Now, after we figured out the reason for not connecting, the question is: would it be possible to make the component working when the PASSWORD_VERSIONS returns 10G only? Unfortunately, I have no control over non-development environments.

Best regards,
Phil

I have explained everything in this thread.

Good luck. I am removing the modification email alerts.

Thanks!

Good luck!

Phil, regarding your question "the question is: would it be possible to make the component working when the PASSWORD_VERSIONS returns 10G only? Unfortunately, I have no control over non-development environments", you will have to play with the 'SEC_CASE_SENSITIVE_LOGIN' setting as previously described.

Please look over the link about authentication. The
https://docs.oracle.com/database/121/DB ... m#DBSEG003

Thanks again, Edward, but I was addressing devArt.

Thank you for the provided information. We are now working on creating a test environment with a user, who has PASSWORD_VERSIONS equal to 10G only, in order to reproduce and fix the issue. We will post here when we get any results.

Pinturiccio wrote:Thank you for the provided information. We are now working on creating a test environment with a user, who has PASSWORD_VERSIONS equal to 10G only, in order to reproduce and fix the issue. We will post here when we get any results.

Thank you so much!

Pinturiccio wrote:Thank you for the provided information. We are now working on creating a test environment with a user, who has PASSWORD_VERSIONS equal to 10G only, in order to reproduce and fix the issue. We will post here when we get any results.

Is there an ETA?

We are working on the issue and do our best for reproducing it. We will post here when we get results.

Dear support, any news on the solution? It is rather easy to reproduce I must say?

Regards,
Joost