20081118 building a camel by committee chapter 4 - plembo/onemoretech GitHub Wiki

title: Building a camel by committee, Chapter 4 link: https://onemoretech.wordpress.com/2008/11/18/building-a-camel-by-committee-chapter-4/ author: lembobro description: post_id: 425 created: 2008/11/18 21:17:12 created_gmt: 2008/11/18 21:17:12 comment_status: open post_name: building-a-camel-by-committee-chapter-4 status: publish post_type: post

Building a camel by committee, Chapter 4

Sometimes the inconsistencies in the identity components of various Oracle products really crack me up.

Take, for example, the alternate realities of case sensitivity of user names and passwords in their E-Business Suite as compared with Internet Directory.

From MetaLink Note 295606.1, “Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting Guide”:

4.14 Case sensitivity for Usernames and Passwords

In Oracle E-Business Suite, passwords are case insensitive; in Oracle Internet Directory they are case sensitive. As Oracle E-Business Suite does not store the case information for passwords, passwords are migrated into Oracle Internet Directory in lower case.

In Oracle E-Business Suite, user account names are case sensitive, whereas in Oracle Internet Directory they are case insensitive. If there are Oracle E-Business Suite accounts that differ only by case, they will need to be resolved before loading into Oracle Internet Directory.
In Oracle E-Business Suite, user account names can have leading or trailing spaces; Oracle Internet Directory does not allow this, and will trim the spaces when loading them.

You can’t make this stuff up.

Bad enough that passwords in EBS aren’t case-sensitive, and therefore are completely unacceptable from a security best practices standpoint, but to continue enforcing case sensitivity of user names when integrated with another product you publish where user IDs are case-insensitive? That takes real talent.

(Yes Larry, I’m making fun of you again)