> ># utaMailAlias -- email alias value > > attributetype ( 1.3.6.1.4.1.19638.1.1.102 NAME 'utaMailAlias' > > DESC 'Email alias' > > SUP mail) > > > Don't SUP it. Use your OID for the NAME, and use the same SYNTAX as the > mail attribute. ;) Here is a theoretical question that I'll ask to see if someone has experience with it. If I change the above attributetype definition, but currently have attributes of that type in my directory, will lead to problems? I'm not familiar with the underlying structure used to store or index these attributes in the backend to know how to predict the results. I'll likely err on the side of caution and remove then reload those attributes unless someone can assure me that it isn't necessary. -- Digant C Kasundra Enterprise Operations and Systems Office of Information Technology University of Texas at Arlington Ph: 817-272-2208 GnuPG Public Key: http://omega.uta.edu/~digant/digant.gpg.asc To request technical support, please contact our computing Help Desk at 817-272-2208, e-mail helpdesk@uta.edu or create a work order at https://eservices.uta.edu/oitforms/workorder.html
Attachment:
signature.asc
Description: This is a digitally signed message part