User Id Case Insensitive Login

Hi All,
I am using jdev version 11.1.1.6.0.
My use case is I want to do use ID case insensitive login.
In weblogic Console Security Realms>myrealm >Providers , we used Providers to do authentication in sequence as below.
1)DefaultAuthenticator-WebLogic Authentication Provider
2)DefaultIdentityAsserter-WebLogic Identity Assertion provider
3)AlfaAesarADAuthenticator-Provider that performs LDAP authentication
4)AlfaAesarDBAuthenticator-Provider that performs DBMS authentication
Is there any configuration option in weblogic console to do user ID Case Insensitive login.
Please help me out in this regard.

Hi, Vivek
In Portal Go to System Administration->System Configuration->UM Configuration->Direct Editing
find out following
ume.logon.security_policy.userid_lowercase=0
and change to
ume.logon.security_policy.userid_lowercase=1
save and restart the server.
regards,
kaushal

Similar Messages

RDBMS Authentication - Case insensitive login

I am using the out-of-box RDBMS authentication realm, to authenticate against the
USER_SECURITY table in the portal database. How do I ensure that usernames are
case insensitive?
Thanks
Kunal

Yup. I am actually changing the user_security table to store usernames in all lowercase.
Sucks!
"Steven Bennett" <[email protected]> wrote:
>
Kunal ,
I am not aware of a way to change this, sorry.
One messy way to do it is to hand crank some of the most obvious combinations
(ALL CAPS. Title Case). But very very very messy
Steve
"Kunal Mittal" <[email protected]> wrote:
I am using the out-of-box RDBMS authentication realm, to authenticate
against the
USER_SECURITY table in the portal database. How do I ensure that usernames
are
case insensitive?
Thanks
Kunal

Password Case inSensitivity

Hello,
Is there a way to make user password case insensitive in OID?
If not is there a way to convert the password to lower/upper case before it stores in OID and then during authentication, convert the user entered pwd to same case before comparing ?
OID version : 10.1.2
Regards

This might be possible using the password policies, check the OID manual section on password policy.
If it is not you can customize it using plugins. You would need a add and modify plugin to make the password lowercase before storing it, and a compare and a bind plugin to convert it when the user is loging on.
Regards,
Luis

Case insensitive user login

Hi,
I am working on a Weblogic portal application (Weblogic 10.3.2) to be deployed in a Weblogic Server 10.3.2. I want to enable case insensitive user name login for my application. Looks like by defaule user name goes for a case sensitive authentication. Is there any way to enable case insensitive authentication? Thanks.
Regards,
Ramakrishnan

Hi
By default Weblogic Login UserId is Case-InSensitive. For quick testing, open your Weblogic Console and say if your admin user id is "weblogic", just try any combination of this value like "WEBloGiC" with his password. It works and you should be able to login.
NOW if you have any External LDAP configured, still you can login with your userid as Case InSensitive. BUT if you see that some Visitor Entilements or DAs stuff is not getting triggered or working properly, then you can do one setting. In your Weblogic Console, select your external AD Provider (like LDAP, AD etc) and click on the properties tab, where you set the host, port, userbase dn, groupbase dn etc. There you should see another property like a CheckBox named something like "Use Retrieved Username as Principal". What this means is if you say for example login as "RJegGA", the login will be successfull but the value that gets stored in the session in security subject value will be like "rjegga" where rjegga is the actual name coming from external LDAP.
So point is, check the above check box and try again. For any users stored in the Default Weblogic Authenticator itself, it is case insensitive.
Thanks
Ravi Jegga

Case Insensitive Search coupled with "LIKE" operator.

Greetings All, I am running Oracle 11gR1 RAC patchet 25 on Windows X64.
This db supports and application that requires case insensitive searches.
Because there are a few entry points into the db I created an "after login" trigger:
CREATE OR REPLACE TRIGGER MyAppAfterLogon_TRGR
AFTER LOGON
ON DATABASE
DECLARE
vDDL VARCHAR2(200) := 'alter session set nls_comp=''linguistic''';
vDDL2 VARCHAR2(200) := 'alter session set nls_sort=''binary_ci''';
BEGIN
IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN
EXECUTE IMMEDIATE vDDL;
EXECUTE IMMEDIATE vDDL2;
END IF;
END MyAppAfterLogon_TRGR;
This ensures that everyone connecting to the DB via any mechanism will automatically have case insensitive searches.
Now, to optimize the know queries I created the standard index to support normal matching queries:
select * from MyTable where Name = 'STEVE';
The index looks like:
CREATE INDEX "CONTACT_IDX3 ON MYTABLE (NLSSORT("NAME",'nls_sort=''BINARY_CI'''))
This all works fine, no issues.
The problem is when I write a query that uses the "LIKE" operator:
select * from MyTable where Name like 'STEV%';
I get back the record set I expect. However, my index is not used? I can't for the life of me get this query to use an index.
The table has about 600,000 rows and I have run gather schema stats.
Does anyone know of any issues with case insensitive searches and the "LIKE" clause?
Any and all help would be appreciated.
L

I think there is issue with your logon trigger :
"IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN"
it should be :
IF UPPER(USER) = 'MYAPPUSER' OR UPPER(USER) = 'MYAPPREPORTINGUSER' THEN
because user name stored in Upper case. Check and try.
HTH
Girish Sharma

Local net users - usernames case sensitive

I am facing an annoying issue with our WLC's 5508.We have configured some local accounts - local net users and we found out that usernames are case sensitive.For example when i setup an account with username:TEST and the then try to login with username:test i get authentication failure..
I thought that only the admin accounts were case sensitive.
Has anyone else faced this problem?Is there any solution for this as i have already configured 60 local accounts.
Thank you in advance.

#Management Usernames are case sensitive.
#Local net user seem to be case sensitive per below bug, however it is a old one on 4.0.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsg72444
*for local netuser, Does WLC allows to create same usernames like this - Apple, APPLE, AppLe. If allowed then at this point its considered that wlc allows to create case insensitive users for local netusers. Else if only Apple is allowed then it is case sensitive for user creation.
*Now try to login like - apple, aPPLE and also like Apple, APPLE, AppLe.
*Share the result along with the tested wlc code for conclusion. Let see what works and doesn't.

Oracle 11g database & OBIEE 10g user id case sensitivity

Hi,
Previously we used to point OBIEE to 10g database and the following query used to return data. But now we have database upgraded to 11g R2. Is there a way to make the 11g R2 database case insensitive and make the following query return results? Here when EMP_LOGIN = upper(bmiller) query is working, but not when EMP_LOGIN = bmiller.
select T32660.X_DISTRICT as c1,
count(distinct case when T32385.OPTY_WID > 0 then T32385.OPTY_WID end ) as c2
from
W_POSITION_H T37785 /* Dim_W_POSITION_H */ ,
W_POSITION_D T36585 /* Dim_W_POSITION_D */ ,
W_EMPLOYEE_D T32660 /* Dim_W_EMPLOYEE_D */ ,
W_OPTY_D T31547 /* Dim_W_OPTY_D */ ,
W_ORG_D T31796,
W_REVN_F T32385 /* Fact_W_REVN_F */
where ( T32385.PR_TEAM_POS_WID = T36585.ROW_WID
and T31547.ROW_WID = T32385.OPTY_WID
and T31796.ROW_WID = T32385.PR_ACCNT_WID
and T32385.PR_TEAM_EMP_WID = T32660.ROW_WID
and T36585.ROW_WID = T37785.SUB_POSITION_WID
and T37785.EMP_LOGIN = upper('bmiller')
and T37785.EMP_LOGIN = 'bmiller' )
group by T32660.X_DISTRICT
order by c1
Thanks
MNRK

If this query was working in the old system, my assumption is that something was changing your session's NLS_COMP to Linguistic. If OBIEE isn't issuing that ALTER SESSION in a login script, the next most likely scenario would be a login trigger that was issuing the ALTER SESSION when the OBIEE user logged in. That trigger would have remained in place had you used the DBUA to upgrade. If you did an export and import, however, it's possible that you didn't export the login trigger.
Justin

Case Sensitive logins

Hello,
We're using Weblogic 8.1.
If I create a user, tmui. Weblogic ignores the login case when I login using
ServletAuthentication. The password is case sensitive.
How can I make the login value case sensitive as well? I should not be allowed
to login with TMUI.
thanks,
Tom

I suspect it is the authentication provider that is case-insensitive. What
authentication provider are you using? If you are using a case-insensitive
one (eg: the NT realm via the compatibility realm), then it is the realm
that is case-insensitive, not WLS.
- Neil
"Tom" <[email protected]> wrote in message
news:3ffb26eb$[email protected]..
>
Hello,
We're using Weblogic 8.1.
If I create a user, tmui. Weblogic ignores the login case when I loginusing
ServletAuthentication. The password is case sensitive.
How can I make the login value case sensitive as well? I should not beallowed
to login with TMUI.
thanks,
Tom

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

How do I convert a case sensitive drive to a case insensitive drive?

I have recently purchased a MacMini Server, and installed the 2 internal hard drives in a RAID 0 configuration to obtain the speed and 1 TB capacity, but unfortunately (rather stupidly in retrospect) formatted the drive in case sensitive mode.
On installing the operating system and multiple applications, everything seemed to work well until I tried to install Adobe Acrobat X Pro. This application refuses to install on a case sensitive formatted drive, which I now understand is a common problem.
The question is how can I convert to a case insensitive format without reinstalling all of the software from scratch?
I have a Time Machine backup, and the easiest thing for me would be to reformat the drive, and then restore from the Time Machine backup.
Will this process work? Or will there be some complications and files that will not function if they were originally installed on a case sensitive drive?
Any help is appreciated....

iPartition can do it ( http://www.coriolis-systems.com/iPartition.php ).
from iPartition Help:
Make Case Sensitive/Case Insensitive
HFS+ now supports a case sensitive format as well as the usual case insensitive format. On a case sensitive volume, the names “Readme”, “README” and “ReadMe” would all represent different files, even if they were in the same folder.
This option allows you to non-destructively change a case sensitive volume into a case insensitive one, and vice-versa. If you are going from a case sensitive volume to a case insensitive volume, some of your files may be renamed automatically by iPartition so that they do not clash. If all of the files in the table below were in the same directory, the right hand column shows the new names iPartition would choose for them:
Old name New name
README.txt README.txt
ReadMe.txt ReadMe 1.txt
Readme.txt Readme 2.txt
README README
ReadMe ReadMe 1
Readme Readme 2
Notice that iPartition puts the number before any file extension.
N.B. iPartition does not transform filenames with numbers on the end back into their original forms. There is no way to tell which files were renamed by the user and which were renamed by the conversion process.

SELECT Query to get the Values in Case insensitive Format

Hi ,
This is hari,
I want to select the user name in a table ex: username="HARI" or username='Hari' or username="HaRi" like this
If i wrote the query like
select username from userdb where username="Hari";
it is displaying the records which only matches "Hari" only .
can anybody help me out on this query asap please....
the query should return all the results
which matches any of the following strings as inputs "HARI" or "HaRi" or "hAri" or the like.
Awaiting for Response,
Thanks & Regards
Hari

Another solution is setting NLS_SORT to CI - case insensitive (or whatever_your_language_is_CI) and NLS_COMP to ANSI:
SQL> with t as (
2             select 'HARI' name from dual union all
3             select 'Hari' name from dual union all
4             select 'HaRi' name from dual
5            )
6 select *
7    from t
8    where name = 'hArI'
9 /
no rows selected
SQL> alter session set nls_sort = binary_ci
2 /
Session altered.
SQL> alter session set nls_comp=ansi
2 /
Session altered.
SQL> with t as (
2             select 'HARI' name from dual union all
3             select 'Hari' name from dual union all
4             select 'HaRi' name from dual
5            )
6 select *
7    from t
8    where name = 'hArI'
9 /
NAME
HARI
Hari
HaRi
SQL> SY.

Case Insensitive Indexes

In relation to switching on case insensitive queries using
alter session set NLS_COMP=LINGUISTIC;Can anyone answer the following?
>
Yes, it works.... but I can't for the life of me figure out how to build a linguistic index that the LIKE clause will actually use. Building an index thus, for example:
create index bin_ai on names(NLSSORT("NAME",'nls_sort=''BINARY_AI'''));
makes an index which does get used to good effect by queries such as
select name from names where name = 'Johny Jacobson';
but not by
select name from names where name like 'Johny%';
Hence, in a real-world test with 100,000 records, the LIKE query runs about 100 times slower than the '=' query (3 sec compared to 0.03 sec). Not very scalable. Is there a way to speed this up??
Also is it possible to set session variables such as nls_comp on a database/schema/user level?

Hi,
select name from names where name like 'Johny%';Performance when using the SQL "like" clause can be tricky because the wildcard "%" operator can invalidate the index. For example a last_name index would be OK with a "like 'SMI%'" query, but unusable with "like '%SMI%'.
One obscure trick for indexing queries "like '%SON'" is to create a REVERSE index and them programmatically reverse the like clause to read "like 'NOS%'", effectively indexing on the other side of the text.
You might want to look at Oracle*text indexes, if your database has low DML:
http://www.dba-oracle.com/oracle_tips_like_sql_index.htm
If you are 10gr2:
Oracle 10g release 2 has now introduced a case insensitive search method for SQL that avoids index invalidation and unnecessary full-table scans. You can also employ Oracle text indexes to remove full-table scans when using the LIKE operator. Prior to Oracle10g release 2 case insensitive queries required special planning:
1 - Transform data in the query to make it case insensitive (note that this can invalidate indexes without a function-based index):
create index upper_full_name on customer ( upper(full_name));
select full_name from customer
where upper(full_name) = 'DON BURLESON';
2 - Use a trigger to transform the data to make it case insensitive (or store the data with the to_lower or to_upper BIF.
3 - Use Alter session commands:
alter session set NLS_COMP=ANSI;
alter session set NLS_SORT=GENERIC_BASELETTER;
select * from customer where full_name = 'Don Burleson'
Hope this helps. . .
Don Burleson
Oracle Press author

Case sensitive and case insensitive Search

Hi friends,
     Iam doing an Search RFC which will search records based on the search parameters provided at the portal side.
One of the search parameter is a field with 40 character which holds the description(title) of the record.
With this search paramter iam facing case sensitive problem.
Example:
Values in Database Table: ( Can be in any case)
       Record 1: Sensitive
       Record 2: SENSITIVE
       Record 3: SensTive
       Record 4: sensitive
       Record 5: sensTive
     Input to RFC: sens*
     Output: Getting only 4rth and 5th record but not all the records.
       The same is the case with the remaining search parameters(Like user name..).
       Is there any way of getting all the records when searching from the data base (with case insensitive).
       Kindly let me know if there is any possibility.
Thanks in advance.
Regards,
Swarna Munukoti.

Generally, no. So, you'll either have to use EXEC SQL, or add more fields to the table. You can do this using APPEND structures, which is the SAP approved way of adding fields. If there are suitable user exits in the standard SAP code, then you'll be able to populate the additional fields there, as new records are created, or amended.
Alternatively, create your own Z table with the same key as the standard table and a "search field" which contains the uppercase version of the field you're wanting to search. You can either, again populate in suitable user exits, or, in worst case, have job that runs regularly populating your Z table.
matt

Case insensitive search and index

I have to execute a case insentitive search.
I created this index on a not null field:
create index indx_prova on
table (nlssort(campo, 'NLS_SORT=BINARY_CI'));
The select is:
select * from tabella where campo like 'A storage%'
This select should retrive 5 records:
A storage ring for crystalline beam studies
a storage ring for crystalline beam studies
A Storage Ring for Crystalline Beam Studies
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
Instead I got only 3 records:
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
So The query isn't case insensitive.
I can't set nls_sort=BINARY_CI and nls_comp=LINGUISTIC at level session.
Is there a solution.
Am I doing something wrog?

I set alter session set nls_comp=LINGUISTIC; alter session set nls_sort=BINARY_CI;
I create this index:
create index titolo_indx on
table (nlssort(campo, 'NLS_SORT=BINARY_CI'));
If I execute this query:
select * from ri01_prodotti where titolo like 'A storage ring f%'
Oracle doesn't user the index.
SQL_ID 7yvspnyf96vp8, child number 0
select * from ri01_prodotti where titolo like 'A storage ring%'
Plan hash value: 350479533
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | | | 2020 (100)| |
|* 1 | TABLE ACCESS FULL| TABLE | 1 | 1365 | 2020 (1)| 00:00:25 |
Predicate Information (identified by operation id):
1 - filter("CAMPO" LIKE 'A storage ring%')
If I execute a query with =, oracle use index.
select * from table where campo ='A storage ring for crystalline beam studies'
SQL_ID 5jzr5nm6b37pq, child number 0
select * from ri01_prodotti where titolo ='A storage ring for crystalline beam
studies'
Plan hash value: 3866031381
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | | | 151 (100)| |
| 1 | TABLE ACCESS BY INDEX ROWID| RI01_PRODOTTI | 377 | 502K| 151 (0)| 00:00:02 |
|* 2 | INDEX RANGE SCAN | TITOLO_INDX | 151 | | 3 (0)| 00:00:01 |
Predicate Information (identified by operation id):
2 - access("RI01_PRODOTTI"."SYS_NC00078$"=HEXTORAW('612073746F726167652072696E6720
666F72206372797374616C6C696E65206265616D207374756469657300') )

How to create case-insensitive account name report?

We have an account report that allows users to enter part of an account name and return matching results. The prompt is case sensitive but I would like it to be case insensitive. This report uses a report prompt and not a dashboard prompt (if it makes a difference), and I can switch to dashboard prompt if necessary.
Since the left pane search for Account Name is case-insensitive and you can select case-insensitive when creating account list views, I am hoping there is a way to apply this same functionality to a report.
I understand I can convert Account Name to upper or lower and tell people to search that way, but that will be a last resort.
Any suggestions on how to make the prompt value and report results for Account Name case-insensitive?
Thanks.
Edited by: user9530733 on Sep 30, 2010 10:51 AM

Similarly to all this, and even what the OP is looking to accomplish, is the habit of developers attempting to coerce the database object names into the format of their language - usually .net or some such. So they create tables named something like EmpDepProjectStatus which may make their application code all look consistent, but becomes EMPDEPPROJECTSTATUS when created in the database. Why can they not adapt to the database and name the table EMP_DEP_PROJECT_STATUS so that we do not go blind trying to manage their db objects? Is it their teachers that tell them EveryThingMustBeWrittenLikeThisBecauseTheyCannotStandSeperatingTheWordsThatNameObjectsWithSpaces_WHICH_ARE_UNDERSCORES_IN_MOST_ALL_LEGACY_LANGUAGES?
I do not think that Oracle will ever become case sensitive. Just like COBOL, IMS, IDMS, JCL, BASIC, PL/I, etc. There is just too much code out there that ignores case that it could not be done.
Unless, of course, Oracle creates a init.ora option to set case sensitive. But I doubt (hope most sincerely) that they will never do that.

User Id Case Insensitive Login

Similar Messages

Maybe you are looking for