Username is case sensitive in BPM Worklist

HI
I have BPEL process with human task, that assigned to jcooper.
When i login as jcooper i see this task.
But if i login as JCOOPER i don't see task.
Why i have 2 users with same usernames.
How it fix.
Thanks.

You could change the worklist application by forcing the username after logon to lowercase. This is done by changing the JSP/java code of the application.
Marc
http://orasoa.blogspot.com

Similar Messages

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.

[Solved] Username case sensitivity when logging in via BASIC authentication

Hi,
Quick question... where the web.xml file defines BASIC authentication for an app, can a change be made somewhere to make the username case INsensitive ?
.. such that passwords remain case sensitive but usernames can be upper/lower regardless of how they are stored (in the database in this case, via DBTableOraDataSourceLoginModule).
I was thinking I could add an upper(supplied_username) function wrapper somewhere before the supplied username / stored username are compared.. what class/file would I need to edit to try that solution?
If not possible.. would form authentication be a better option for case insensitivity, and if so would it be difficult to hookup a custom login form to the DBTableOraDataSourceLoginModule instead of the BASIC login window ?
Thanks..

Hi,
by default all username and password is cases sensitive - no matter how the logon is performed. The DBTableOraDataSourceLoginModule provides an option to handle passwords case insensitive (as explained in the documentation !)
http://download-uk.oracle.com/docs/cd/B32110_01/web.1013/b28957/loginmod.htm#BABHDJAH
casing
=====
The case-sensitivity when comparing login user names to names in the database. Use sensitive to require case-sensitive comparisons, toupper to convert the login user name to all-uppercase, or tolower to convert the login user name to all-lowercase. (If anything other than these three values is specified, the default value will be used.)
Default: sensitive
Example: toupper
Frank

Not case sensitive input of username?

I have a login section that has a username and password input
field. I am not sure if I am doing this right, but since there is
only one username and one password, this is how I did this.
function checkPassword(userN:String, passW:String):Void {
if(userN == "collections" && passW == "winter2008"){
//let user proceed
}else{
//error message
My question now is how can I have the username not be case
sensitive. Is that possible?
Thanks a lot for any help!

You can use the toLowerCase(), or toUpperCase() methods to
give you a string that you can reliably compare. You may also want
to sort out any stray space characters that the user may type in.
Try something like this:

How do I make the my login page username field not case-sensitive?

Can anyone tell me how to make my username field not case-sensitive?
This is my code
<html>
<body>
<%@ page import="java.sql.*" %>
<%
String username = request.getParameter("username");
String password = request.getParameter("password");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
Connection login = DriverManager.getConnection("jdbc:odbc:Testing","abc","abc");
Statement stmtLogin = login.createStatement();
String sqlLogin = "SELECT UserName, UserPassword FROM Users WHERE UserName='"+username+"'";
ResultSet rsLogin = stmtLogin.executeQuery(sqlLogin);
while(rsLogin.next())
String suser = rsLogin.getString("UserName");
String spass = rsLogin.getString("UserPassword");
if(username.equals(suser) && password.equals(spass))
HttpSession mysession = request.getSession(true);
mysession.setAttribute("username",request.getParameter("username"));
response.sendRedirect("hello.jsp");
else if(!(username.equals(suser) && password.equals(spass)))
response.sendRedirect("index.jsp?message=Invalid%20Username%20or%20Password");
login.close();
%>
</body>
</html>

if(username.equalsIgnoreCase(suser) && password.equals(spass))Hope this helps!

Username - case sensitivity and embeded period

I have been asked to investigate the impact of syncing our oracle user names with our AD names .. which would mean putting a period (dot) in the username. (example - john.doe). First attempt to create one returned an error which lead to the following testing:
SQL> conn system/****
Connected.
SQL> --
SQL> -- create a user with a dot in the name
SQL> --
SQL> create user ed.stevens identified by tiger;
create user ed.stevens identified by tiger
ERROR at line 1:
ORA-01936: cannot specify owner when creating users or rolesOk, the '.' is seen as a delimiter, so must be quoted, probably leading to case sensitivity.
SQL> create user "ed.stevens" identified by tiger;
User created.
SQL> grant create session to ed.stevens;
grant create session to ed.stevens
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> grant create session to "ed.stevens";
Grant succeeded.
SQL> select username
2    from dba_users
3    where upper(username) like 'ED%'
4    order by 1;
USERNAME
ed.stevens
1 row selected.Now let's do it with an upper case name
SQL> --
SQL> create user ED.STEVENS identified by lion;
create user ED.STEVENS identified by lion
ERROR at line 1:
ORA-01936: cannot specify owner when creating users or roles
SQL> create user "ED.STEVENS" identified by lion;
User created.
SQL> grant create session to ED.STEVENS;
grant create session to ED.STEVENS
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> grant create session to "ED.STEVENS";
Grant succeeded.
SQL> select username
2    from dba_users
3    where upper(username) like 'ED%'
4    order by 1;
USERNAME
ED.STEVENS
ed.stevens
2 rows selected.Everything to here makes sense. Now lets' try to connect as these two nefarious characters!
SQL> --
SQL> conn ed.stevens/tiger
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> select user from dual;
SP2-0640: Not connected
SQL> conn "ed.stevens"/tiger
Connected.
SQL> select user from dual;
USER
ed.stevens
1 row selected.
SQL> --
SQL> conn ED.STEVENS/lion
Connected.Whaat?? Why wasn't the '.' seen as a delimiter here? This is the question that this example was leading to.
SQL> select user from dual;
USER
ED.STEVENS
1 row selected.
SQL> conn "ED.STEVENS"/lion
Connected.
SQL> select user from dual;
USER
ED.STEVENS
1 row selected.
SQL> --
SQL> spool off
SQL> conn system/****
Connected.
SQL> drop user "ed.stevens";
User dropped.
SQL> drop user "ED.STEVENS";
User dropped.

Centinul wrote:
Ed --
I saw different behavior in my environment:
SQL> CREATE USER "cen.tinul" IDENTIFIED BY mynx;
User created.
SQL> CREATE USER "CEN.TINUL" IDENTIFIED BY mynx;
User created.
SQL> GRANT CREATE SESSION TO "cen.tinul";
Grant succeeded.
SQL> GRANT CREATE SESSION TO "CEN.TINUL";
Grant succeeded.
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> CONNECT cen.tinul/mynx
Connected.
SQL> SHOW USER
USER is "CEN.TINUL"
SQL> CONNECT CEN.TINUL/mynx
Connected.
SQL> SHOW USER
USER is "CEN.TINUL"
"This just gets curioser and curioser."
This is the system I used for the test posted above - running on 32-bit OEL under vmware on my laptop
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE10.2.0.4.0Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5 rows selected.So I ran the test against our prod datbase, running under 64-bit HP-UX Itanium
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5 rows selected.As for what about the two is not shown, the 32-bit Linux was built with the 10.2.0.1 base install, then the 10.2.0.4.0 patchset, then the Oct 2009 CPU - all before creating the database. The database was created from scripts using CREATE DATABASE, as generated originally by dbca (not the 'restore database' scripts from dbca when using one of their pre-defined templates.)
The HP-UX system was built as a 10.2.0.1 database, upgraded to 10.2.0.4, and has all CPU's through Jan 2010.
Both systems gave exactly the same results, which are obviously different from yours ....
A mystery wrapped in an enigma ....

Case sensitive usernames for wiki

Hi I'm running the wiki services which get the usernames and passwords from another server which have upper and lowercase usernames, is there a way to ignorecase on usernames for the wiki? so if i type
MSmith or msmith it still lets them login?

Hi,
AFAIK usernames whether Full or short names are case sensitive in OD. The wiki uses Password Server to authenticate against a user account. UserManagementv10.5.mnl for 10.5 Server describes the Open Directory creation and modification of a user account and the rules for Full and Short names. Case insensitivity is not covered.
Using an add on script such as LDAP authenticators communicating with OD can implement any policy you want. But out of the box OD is case sensitive.
HTH,
Harry

How to Enable the Oracle BPM Worklist?

Hi!
Newbie here.
So how do you enable the Oracle BPM Worklist?
Sure there a tutorial for this found in http://docs.oracle.com/cd/E21764_01/doc.1111/e17366/chapter16.htm#BABHCICI
and in section "16.2 How to Enable the Oracle BPM Worklist" it says
"By default, Oracle BPM Worklist functionality is disabled. You can enable this functionality in AIAConfigurationProperties.xml.
To enable the Oracle BPM Worklist:
-Access AIAConfigurationProperties.xml located in <AIA_HOME>/aia_instances/$INSTANCE_NAME/AIAMetaData/config.
-Set the EH.INVOKE.HWF property value to true.
-Reload updates to the AIAConfigurationProperties.xml file."
However upon searching for the file "AIAConfigurationProperties.xml" or even the directory "aia_instances" in our servers, I could not find them. Please help me!

If you are talking about 11g Worklist app, then you won't be able to do that, since the source code is not shipped with the product. The better way is to create the custom worklist application using the Worklist APIs. Refer to the SOA Developers Guide.
In case of 10g, you can access the source code of Worklist app, even in that case, you can do your requirement using the exposed APIs.

Customization of Human tasks the BPM Worklist App with ADF App

Hi All,
We are building a custom ADF application which aims to combine several business process human tasks to a unified interface.
And how to integrate the Human Task Flow BPM Worklist to my ADF App.
Otherthan that
To the BPM Worklist App we want to do customizations also like
1.Want to customize to apply our own custom skins to customize banner logo, title to the BPM Human Task Flow App.......
2.And based on the logged in user/role we wanted to restrict the features of the Work List App.
Say for Example should not provide the Facility to Add New Page if the logged in user is not an Admin, like wise no provision to add or modify or delete the Worklist Views like that...
How to get control the App based on User/Role
Any help or pointers would be appreciated!
I have ADF Experience from projects Using JDeveloper 11.1.1.5.
But, for me this is the first BPM case.
Renuka

Hi Renuka,
There are basically two ways to create an ADF UI for a BPM Task:
1. Generate it from the task
2. Create a ADF Taskflow based on Human Workflow Task
Since I tell this by heart, I might be slightly wrong in the terms.
You probably want to try the second option. It is accessible from the "New Gallery". You'll have to provide the Human Task from the BPM project, but then you can build up the ADF Taskflow by your self, based on the customizations of the rest of your application.
Should not be rocket science for someone with ADF11g experience. Since it is not my dayly job, I need to figure it out every time again ;). But I did it in the past and it wasn't so hard.
Regards,
Martien

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

Case sensitive variabe

Hi,
I am using a variable and in my PL/SQl function/procedure .But the problem i face is the variable is being converted into UPPER CASE Automatically.i have to retain the case of my string.I can't use to_upper or to_lower or NLS_UPPER or NLS_LOWER.Because
if my string is PRaMOd
by Default it takes PRAMOD
if i use NLS_LOWER its pramod.
I want PRaMOd as it is.
Is there any way to get that right.
Thanks,
Pramod

Hi,
Oracle strongly recommends that you not use quotation marks to make usernames and passwords case sensitive
But if you like...you can use quoted identifiers:
Connected to Oracle Database 10g Express Edition Release 10.2.0.1.0
Connected as hr
SQL>
SQL> CREATE OR REPLACE FUNCTION "FuNcTiOn_1" RETURN NUMBER AS
2 BEGIN
3     RETURN 1;
4 END;
5 /
Function created
SQL> SELECT * FROM USER_OBJECTS t where t.object_type = 'FUNCTION';
OBJECT_NAME                                                                      SUBOBJECT_NAME                  OBJECT_ID DATA_OBJECT_ID OBJECT_TYPE         CREATED     LAST_DDL_TIME TIMESTAMP           STATUS TEMPORARY GENERATED SECONDARY
ExAMple2                                                                                                             17867                FUNCTION            16/07/2009 16/07/2009 20 2009-07-16:20:34:00 INVALID N         N         N
FuNcTiOn_1                                                                                                           17872                FUNCTION            16/07/2009 16/07/2009 20 2009-07-16:20:34:57 VALID   N         N         N
F_TEST1                                                                                                              16266                FUNCTION            01/06/2009 01/06/2009 10 2009-06-01:10:33:32 VALID   N         N         N
F_TEST2                                                                                                              16267                FUNCTION            01/06/2009 01/06/2009 10 2009-06-01:10:33:51 VALID   N         N         N
FNC_TEST                                                                                                             17667                FUNCTION            11/07/2009 11/07/2009 09 2009-07-11:09:36:57 VALID   N         N         N
FNC_RANDOM_MIXED_VALUE                                                                                               14116                FUNCTION            15/04/2009 15/04/2009 23 2009-04-15:23:59:32 VALID   N         N         N
FNC_COMPARE_STRING                                                                                                   14221                FUNCTION            19/04/2009 19/04/2009 15 2009-04-19:15:31:05 VALID   N         N         N
EVAL                                                                                                                 16620                FUNCTION            08/06/2009 08/06/2009 20 2009-06-08:20:18:13 VALID   N         N         N
8 rows selected
SQL> Regards,

How to select a case sensitive value in SQL with C#

Hello,
I have an application that at the begining a user will login with a user name and password which is stored in the database. The SQL statement is as follows:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' AND passWord='" + txtPassword.Text + "'";
For testing purposes I have set the password to the word test. The problem is, if the user enters in TEST or TeSt or TESt it will grant them access. How do I set it to force the correct case?
I am using SQL 2005 for the database.
Thanks!
~zero

You can also set Collation while comparing strings:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' COLLATE Latin1_General_CS_AS AND passWord='" + txtPassword.Text + "' COLLATE Latin1_General_CS_AS";
All comments about not doing this type of quering using command string, instead of command with parameters, they are apsolutely right.
Nevertheless i will have only username as a parameter in the command and password will be return value from procedure. I will check for equality of entered password and returned one from command in C# code, and C# is case sensitive. There is a good security model implemented for password in AdventureWorks sample database for SQL Server 2005, in table Person.Contact.
That model use two fields for password, PasswordHash and PasswordSalt. PasswordSalt is randomly generated hash when password is modified and with that salt, password string is encrypted, which produce PasswordHash. So when you want to authenticate a user, execute a command that will return a row(PasswordHash and PasswordSalt) for entered username, and in application you will encrypt entered username with PasswordSalt. If generated string is equal with the one returned PasswordHash, then you have a valid login. If nothing is returned from command or they are not equal, you have invalid login.

Login - is it case sensitive?

Hi everyone,
I'm using WLS4.0 SP2 with iPlanet LDAP server, and seeing a peculiar thing.
When a user login to the portal, and types username with different case
(lowercase in place of uppercase and vice versa), the portal let the user
login (can see the "customize portal" and "logout" button), but shows no
portlets but the initial welcome page before login. The caching realm setup
for the LDAP server is not case-sensitive. Our network admin also says that
the LDAP server is not case-sensitive.
My question is - where could the source of this peculiar case sensitivity
be? Any insights?
Thanks!
Makoto

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>

Case sensitivity of Cisco UC Apps - CSCur00659

Hi,
Can someone tell the Cisco developers (all of them, in general) that usersnames should NEVER be handled with case!?!
Finesse Agent login is case sensitive, doesn't remember extension and doesn't auto-logout when we close the browser (UCCX 10.5(1)). All due to case sensitive handling of usernames.
We are AD integrated and all usernames have upper case letters.
Regards,
Erik

I ended up solving this as follows.
In plain words, I was creating the install directory on my local desktop and uploading to Azure. Publishing Wizard was creating pointers to local directory. Had to specify where files were being published in the Updates tab.
In the Publish Tab, here were my settings:
Publishing Folder to c:\...
Installation Folder to http://<mydomain>.blob.core.windows.net/<myprojectname>install
App is available offline (checked)
Then Under Application Updates:
The Application should check for updates Checked, Before the App starts checked
Update Location (if different than publish) points to the same <a href="http://.blob.core.windows.net/<myprojectname>install">http://<mydomain>.blob.core.windows.net/<myprojectname>install <this is what I was missing>
To compound matters, I had a minor typo in the myprojectname so make sure they are "identical". I think case does matter here.
The reason it would work sometimes is that after checking the manifest (if found I was out of date, it was trying to load media from the C: drive and resulting in 404 source file not found errors. On my development machine, those files were there.
This is why I thought it might be a case problem.
Ed

Users are not able to login to BPM worklist application from one of the AD.

Hi ,
We are using FMW11g ( 11.1.1.6.0) and configured 2 AD's.( AD-1 & AD-2). We are able to see users from both AD's in the weblogic admin console. Users present in AD-1 are able to login to BPM worklist application without any issue but users from AD-2 are not able to login to BPM application. Could any one please answer 1) Can we configure 2 AD's to FMW11g ? 2) If "YES" , what configuration needs to change to users login from AD-2.
Please let me know if any more information need.
Regard's
Naveen

Hi
NO. You CANNOT use more than One Security Provider for a BPM Workspace Application. Only the top most first Security Provider will work. In your case you have 2 ADs security providers and only users from top most can login. Yes, you can see the Users from both and infact all the Security Providers that are configured. It is the limitation of the bpm workspace application and its corresponding security framework.
Out of box, if you use default AD Configuration then there is nothing you can do. Only the first top most will work. If you really really want you need to use totally custom authentication provider where you will write your own code for authentication. Remember this development is pure weblogic security related one and you need to have good understanding of internal weblogic security. I would not recommend this.
Here is one old post. This old post has 2 other old posts worth visiting to get more details:
Re: Use multiple ActiveDirectory as authenticator provider
Re: oracle soa and active directory integration (Different requirement/usecase)
Thanks
Ravi Jegga

Username is case sensitive in BPM Worklist

Similar Messages

Maybe you are looking for