marklar23 Absent Member.
Absent Member.
417 views

eDir Object Case Sensitivity for OES11?


I'd ask this in the OES11 forum but don't have access, so I apologize if
this is the wrong place.

When at Brainshare this past October I recall that something was
mentioned in relation to OES11 that eDirectory will become case
sensitive and that the recommendation going forward was to create new
objects in all lower case. Unfortunately I can't remember if it was
OES11 in general or one of the upcoming features that I wanted to
implement when it becomes available(does anyone know what the case is?),
but this brings me to a question/issue.

For over the last decade my tree was created using all uppercase naming
for most everything. When OES11 becomes available will there be a tool
that will help script bulk changes to change all of my necessary objects
from all uppercase to all lowercase as is recommended? Will this also
affect objects in my GroupWise system, if there is something?

I'm asking because as I add staff or change names between now and
whenever OES11 gets deployed in my organization, I am entering names as
all lowercase. New users aren't much trouble, but I've found that when
I change a user's name if they get married/divorced that I need to
manually change both the eDir user object and the GroupWise user object
separately. I'm just trying to figure out if I need to slowly start
changing things now or if there will be a mass operation option at a
later date. Thanks!


--
marklar23
------------------------------------------------------------------------
marklar23's Profile: http://forums.novell.com/member.php?userid=5123
View this thread: http://forums.novell.com/showthread.php?t=448926

Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: eDir Object Case Sensitivity for OES11?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

eDirectory has always had the ability to be case-sensitive, case-aware,
or case-insensitive per attribute. That is not planned to change as far
as I can tell (I asked people who would know) so this may be some change
specifically in OES with regard to how mountpoints for NSS volumes are
setup automatically 'sys' instead of 'SYS' or maybe LUM will become
case-sensitive by default (it was for a while, I think there's now an
option so that it will try to be case-insensitive... whatever) but the
rumor you heard was probably not about eDirectory itself.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO1m0YAAoJEF+XTK08PnB5X2UQAMabflU1HyrQcpLMdzy9/739
42HnZXmOfOfUCZ8CSUa9Iq1RREVF2pThTMmvvMdqhz15iSBqidrHE03r2cRKcg8h
dqQMtJ8OrigKUREYW84c9o+OgmLaJ3UeBtVKab7zMZGhN52d1jG3/9ux78OiEJIj
09TQl2n9krRMF2MTSA7KvfzaiBqwc9nBux/bVMcYG8gN/4VJSJgoVjzbxfGRux9B
Vvs+EKGZ9pWznCoQrqlzqMG+YSNGqE1br0DhnyB0xGMTFOlFSvcLdPseDeMrk8qv
KKSOM/LBaDN5oQKVrzyK6od3Ozy+oLVmkKbvb9uY0ICfppMp8eO4zojuscryUfFi
e6RKFPgdGs0YV2qizJ8MET9WURMh45JnmhTz1ekv/tE5K/08Ii/a6z/YEAYk1qGn
MZlXdnGhfEiNORqZvOFRUu8dBBTCRzZ2MQqhs1zmTuZkRySdAIRtFUagLDNy0oKW
LgM2UESc9mb9Xfsmvy4y2lyIDx5grZt4NpJWzl/OBx5CZ2YzTrwO7pFoNti/jt/3
7qi8DlciUVXfWG+tYF/LWvitVXdfs0AsQb1jPf5QIvQoEJoZ3aG/QBdNedyIBqGZ
PpEiANN9gXrwWCsEhg92pYUG2UUUaCEWEIa5jjwDPPhAar/lWl9GNXxW5Zlu5ecl
dGDS1VLK0RiOij9t9Yvd
=S7E4
-----END PGP SIGNATURE-----
0 Likes
peterkuo Absent Member.
Absent Member.

Re: eDir Object Case Sensitivity for OES11?


In the context of your message, you infer OBJECT NAMES (rather than
their attribute values) are going to be case-sensitive - if this is
going to be true, then it will violate both X.500 and current LDAP
standards, and it will be a totally insane and foolish change, IMHO. I
think you may have missed a few key words in their reference and have
the incorrect "context."


--
peterkuo
------------------------------------------------------------------------
peterkuo's Profile: http://forums.novell.com/member.php?userid=88
View this thread: http://forums.novell.com/showthread.php?t=448926


-- eDirectory Rules! Peter www.DreamLAN.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.