Case-sensitive passwords in 11g

Hello,
This is a rather silly post, but I've been Googling and can't find whether SQL Developer supports case-sensitive login or not. I've read that some other clients always send an "uppercase" password (no matter how you typed it) which causes problems with Oracle 11g. Is SQL-Developer "compatible" with the new 11g case-sensitive policy?
Thank you.

Yes SQL Developer is definitely compatible with 11g case insensitive password.

Similar Messages

Case sensitive password in ECC6.0

Hi All,
I'm using the below code to connect to SAP ECC6 system. The below code works fine when the SAP Logon password is all caps. But, when the password is mixed case I get an Error Message.
* SAPHD hd = SapConnc(argv, sapsys, client, cadsys, user, passw, langu, vers, msg);*
As ECC 6 is case-sensitive, does anyone know any workaround to make sure that case-sensitive password login works from external application on ECC6.0 also.
Thanks in advance,
Naveen

please check parameter
login/password_downwards_compatibility
according to sap help:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/d2/141fb593c742b5aad8f272dd487b74/frameset.htm
Specifies the degree of backward compatibility to be achieved. The default value is 1, where the values have the following meaning:
0
Caution
With login/password_downwards_compatibility = 0, passwords are stored in a format that systems with older kernels cannot interpret. The system only generates new (backward incompatible) password hash values.
1
The system also generates backward compatible password hash values internally, but does not evaluate these for password-based logons (to its own system). This setting is required if this system is used as the central system of a Central User Administration that systems that only support backward compatible password hash values are also connected to the system group.
2
The system also generates backward compatible password hash values internally, which it evaluates if a logon with the new, non-backward compatible password failed. In this way, the system checks whether the logon would have been accepted with the backward compatible password (truncated after eight characters, and converted to upper-case). This is recorded in the system log. The logon fails. This setting is to allow the identification of backward incompatibility problems.
3
As with 2, but the logon is regarded as successful. This setting is to allow the avoidance of backward incompatibility problems.
4
As with 3, but no entry is created in the system log.
5
Full backward compatibility: the system only creates backward compatible password hash values.
Available after SAP NetWeaver 6.40

Oracle 11G password case sensitive option is not working.

Hello,
I am facing problem in Oracle 11G. I installed and created a database. I disabled password case sensitive option by setting it to false (Pls see the below output). but case sensitive option is not disabled and i am not able to logon using the lower case password.
SQL> connect sys/<pwd in lower case>@<connect string> as sysdba;
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> connect sys/<pwd in uppper case>@<connect string> as sysdba;
Connected.
SQL> show parameter SEC_CASE_SENSITIVE_LOGON
NAME TYPE VALUE
sec_case_sensitive_logon boolean FALSE
Any idea.... should i open the case in the metalink ?
With Regards
Hemant Joshi.

Can you execute:
SQL> select USERNAME, PASSWORD_VERSIONS from dba_users where username = 'SYS';Have you tried reseting the sys password? When you create the password file by default the passwords stored on it are case sensitive, maybe you also need to rebuild it...
Enrique
PS. See Note:429465.1 +11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication+
Edited by: Enrique Orbegozo on Oct 15, 2008 1:20 AM

User Password case sensitivity issue.

Hi,
I have been migrated users from EBS to OID, but having some issues like some existing users password in EBS are in Capital letters but when they connect with SSO the same password not accepted, but users can connect same password in small letters.
How I can solve this issue????????
Senario:
1: Existing EBS User:(Before integration of OID+SSO), users are directly connecting with EBS.
User Name: HINA.SARWAR-----------(Not case sensitive)
Password: ABCDEF -----------( Case sensitive)
2: Existing EBS User:(After integration of OID+SSO), user are connecting via SSO.
Eexpected behavior is that users should logon with above pass "ABCDEF", but they cannot.
eg:-
Cannot connect as:
User Name: HINA.SARWAR -----------(Not case sensitive)
Password: ABCDEF -----------( Case sensitive)
Can connect as:
User Name: HINA.SARWAR -----------(Not case sensitive)
Password: abcdef -----------( Case sensitive)
thx

Hi,
The solution to your problem is here at metalink:
Password Case Sensitivity Lost During Extract And Import From EBS to OID [ID 951170.1]
regards

Bugs due to case sensitivity of objects?!

Hi,
When migrating from MSAccess 97 to Oracle
8i, it seems that there are many problems
during the migration due to case sensitivity
of Oracle objects. Specifically, the usage
of the double quoted is not always correct
resulting in JET/DAO 3011 messages. I dont
know in which part of the chain is the
problem though (Access, ODBC or Workbench).
Is it possible, using Workbench wizard to
create and reference all objects in a non-
case sensitive manner (tablespace,
tables ...) to avoid these problems.
If not, any suggestion will be welcome,
-Eric Giguere
[email protected]
null

If you use SSO, then the passwords are case sensitive. If you are not using SSO, then you may need to create table that contains case sensitive passwords and associate them to database passwords.

Case sensitivity in 11g passwords

Hi.
I read that passwords are now "case sensitive" in 11g. Really? I checked below, then I changed the password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> show parameter sec_case_sensitive_logon;
NAME TYPE VALUE
sec_case_sensitive_logon boolean TRUE
SQL> alter user sys identified by TINA;
User altered.
SQL> exit
I try to connect using different case:
sqlplus sys/tINna@orcl as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Sat Dec 19 16:28:43 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
I am a little confused as to how I can connect when I changes the case.
Or do i misunderstand "case-sensitivity"
Thanks

Hello,
In fact it depends on the value of the parameter sec_case_sensitive_logon. You can check its value as follow :
SHOW PARAMETER SEC_CASE_SENSITIVE_LOGONAnd change it as you want:
ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = TRUE;More over, you should check the password version 10g or 11g:
SELECT username, password_versions FROM dba_users;A 10g password is case-insensitive even when case-sensitivity is enabled.
And also it depends on your password file. If it was created with ignorecase=y you'll have
to recreate it:
orapwd file={color:red}orapw_filename{color} entries=100 ignorecase=n password={color:red}password{color}You can find on the following link some information about how to enable case-sensitivity:
[http://download.oracle.com/docs/cd/B28359_01/network.111/b28531/authentication.htm#DBSEG3225]
Hope it can help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Dec 19, 2009 5:59 PM

Network diagnostics is not accepting the WEP password on my wireless router. I know the password is case sensitive and was very careful in entering it but it still gives me the "Unable to join Wi-Fi Network" error message.

I need help setting up the wireless router for my iMac. I did not know the WEP password when I first turned it on to set things up. Now that I know the WEP password I cant get Network Diagnostics to accept it. I know it is case sensitive and was very careful when I entered the password. What should I do?

Hi, unfortunately WEP is about as secure as a bar of gold lent to a Gang Den! It can be broken in under 30 seconds these days!
If the PW is ASCII, try enclosing it in qoute marks, if Hex try preceding it with the & or % sign.
Also, is the Router set to only allow connect ion to MAC addies of the Interface?

I recent la format the drive and create a case sensitive jornal and put a password. How I undo it if I just see the whole drive as the recovery disk

I want to format my computer and I start to do that but I fondo a copy of the boot folder on the drive, not the recovery drive. I formated and make it case sensitive jornal with a password. Then I put a password in main too. So the drive the entre drive become my recovery drive.So I have two recovery drive I think.I learn almost all the diskutil comando and I don know how to fin it. The disks are not showing the one with the passwords.

Hi Kappy,
Just wondering if you had any advice for my situation . . .
My time machine backup was backing up to a drive that was "Mac OS X Enteded Journaled, Case Sensitive." I had no idea what this meant, or that it would even cause issues.
I took my computer to the Apple store yesterday, and they wiped it clean. When they tried to restore it from the Time Machine backup drive, it would not work. Their guess is that Time Machine cannot restore from a drive that is "case sensitive."
Any thoughts on how I can convert my time machine backup data from a "case sensitive" state, to a "non-case sensitive" state? I've tried to just drag and drop the files from the case sensitive formatted drive to a new drive that I have that is formatted non case sensitive, but I get the following error message:
"The volume has the wrong case sensitivity for a backup"
I just really want my data back - I thought TimeMachine was the way to go (and was supposed to work) but unfortunately it is not.
Any help you can provide would be greatly appreciated.
Thanks,

Can i make the database passwords non case-sensitive ??

Can i make the database passwords non case-sensitive ??

Yes: set instance parameter SEC_CASE_SENSITIVE_LOGON to FALSE ( http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams220.htm#I1010299).

Oracle Passwords CASE Sensitive

My Oracle 9i DB is not CASE sensitive on my passwords. I can not find any info on what parameter I can change to make it case sensitive.
All documents I find on net tell me that Oracle is CASE sensitive by default why are my passwords not?
Thanks in advance for any and all help,
David Miller

The topic they are typically were talking about being case sensitive is data insdie oracle db...
Also saw discussiona on use of " " (double quotes) on the ALTER USER command and password to make it specific to case.. Not sure where that came from at all...
Miller

Upon upgrade to 11.2 , will passwords become case sensitive automatically ?

Os : Solaris 10
We are upgrading from version 10.2.0.4 to 11.2.0.3 ? Will the user passwords become case sensitive automatically after the upgrade ?

Tom wrote:
Os : Solaris 10
We are upgrading from version 10.2.0.4 to 11.2.0.3 ? Will the user passwords become case sensitive automatically after the upgrade ?No - you will need to reset existing passwords after the upgrade to take advantage of this feature
http://docs.oracle.com/cd/E11882_01/server.112/e23633/afterup.htm#UPGRD12434
Passwords for accounts created after the upgrade are automatically case sensitive.
HTH
Srini

Making user account logins/passwords case sensitive?

Hi, just a quick question. Is it possible to make user account login/passwords be case sensitive? At the moment they are case insensitive.
Thanks :)

You can make only user account login case sensitive but not password.
SQL> create user "Test" identified by "tEST";
User created.
SQL> grant create session to "Test";
Grant succeeded.
SQL> conn test/test
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> conn "Test"/test
Connected.
SQL>

When logging onto a web site with a log on name firefox is changing logon name from Kostas to kostas as the site is case sensitive it is not acceptable. how do I correct this? Thanks

I registered with a web site and used the name Kostas as the log on name. Entered a question and recieved replies
When I later tried to log onto the web site to say thankyou ,and enter Kostas in the log on box a reminder appears created by Firefox of kostas, I ignore this, move to the password box and firefox changes the log on name to kostas with small k. The register is case sensitive so for quite a while I could not understand what was going wrong? I eventually managed to log on by using a rival system
My previous experience is that if you use a different log on name it is recorded and then you choose the correct one to use? But in this case I am given no choice
How can I correct this please
Probably no connection but
I registerd with another site and recieved an e-mail in which I had to click on web address to confirm registration and came up with an error message, tried a few times and same thing happened?? The webmaster of this site had no record of my registration details?
Finally I had a phone call from a company called NERD-I.com
offering to solve various computor problems at a fee. I did not take up their offer, but hope they do not have anything to do with my current problems??
Many thanks

Hi Corel
Thank you for your reply
However I need the lower case version for some sites and the upper case version for the site in question? To make matters worse this site does not allow you to change your log on name unless it is in the form of an e-mail address
So what I need is Kostas for this site and kostas saved for other sites and allow me to choose which one I want to use
How do I do this please
I have no bother with this on Win Internet Explorer but I like Firefox
Mind it may be as simple as deleting The appropriate entry and resetting with Kostas instead of kostas?
But I would appreciate knowing the correct solution from an expert

Mod_osso.conf - sso protected - case sensitive URL not working

Greetings,
I have modified my mod_osso.conf (see below) file to protect the following URL "http://host.domain.com:7777/test".
If you enter the above URL - you are properly challenged for a user-name and password. HOWEVER, if you enter "http://host.domain.com:7777/TEST" or any other variation /Test, /tEst, /teSt etc. SSO does not get enabled.
I'm missing something, what is it???
Thanks,
Bill G...
mod_osso.conf file
LoadModule osso_module modules/ApacheModuleOSSO.DLL
<IfModule mod_osso.c>
OssoIpCheck on
OssoIdleTimeout off
OssoConfigFile D:\oracle\903_j2ee\Apache\Apache\conf\osso\osso.conf
# BG ADD
<Location /test>
AuthType Basic
Require valid-user
</Location>
</IfModule>

If you are on a UNIX-based server, URLs are always case-sensitive.
Enter an directive for every possible combination, or create the alias/redirect for each combination in the httpd.conf (recommended)
HTH
LLB

Jdbc bug in executeUpdate(sql, int[]) when table name is case-sensitive;

I have found a bug in oracle's jdbc (ojdbc6.jar), can someone tell me how to submit it so that it can be fixed?
The BUG: using executeUpdate(insert_sql_stmt, int[]) to retrieve the generatedKey generated by before-insert trigger using a sequence results in error when the tablename is case-sensitive (but OK if table name in uppercase).
Steps to reproduce:
1a. create table "mixCase" (f1 integer, f2 varchar2(20));
1b. create table upperCase (f1 integer, f2 varchar2(20));
2a. create sequence mixCase_seq start with 1;
2b. create sequence upperCase seq start with 1;
3a. create or replace trigger mixCase_trigger before insert on "mixCase"
bq. for each row \\ begin \\ select mixCase_seq.nextval into :new.f1 from dual; \\ end;
3b. create or replace trigger upperCase_trigger before insert on upperCase
bq. for each row \\ begin \\ select upperCase_seq.nextval into :new.f1 from dual; \\ end;
4a. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into \"mixCase\"(f2) values('aa')",new int[]{1});
4b. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into upperCase(f2) values('aa')",new int[]{1});
When you run 4a or 4b in a java jdbc program:
4b runs OK and rset=stmt.getGeneratedKeys() returns the correct f1 value of 1.
4a results in error:
bq. h6. java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist \\ + at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)+ \\ + at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)+ \\ + at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)+ \\ + ...+
+Notes:</</em>
# If Statement.RETURN_GENERATEDKEYS is used instead of "new int[]{1}" in 4b, there is no error but the rset=stmt.getGeneratedKeys() returned in a ROWID such as 'AAARUyAAEAAAAGQAAL', not what is expected. Other database's jdbc return the correct generated integer value.
# Same 4b error if new String[]{"f1"} is used as 2nd argument for executeUpdate.
# The only difference in 4a and 4b is that 4a has case-sensitive table name. All sequence names, trigger names, column names are implicitly deemed to be uppercase by oracle in both cases.
bq.
Edited by: user10343198 on Oct 2, 2008 5:50 PM
Edited by: user10343198 on Oct 2, 2008 6:34 PM

Please patch one fo your machines to 10.2.0.3 and then try and duplicate. You do not have to go through the complete registration of the XSD process thoguh you can check and see if the c based parser will validate on the command line using the
schema executible under your oracle_home bin directory.
schema 1.xml 1.xsd
for example
if it dupes in 10.2.0.3 open a TAR with support so that we may bug it.
regards
Coby

Case-sensitive passwords in 11g

Similar Messages

Maybe you are looking for