Printout Header
LEX RSS Feed

LEX Online Manual Content

Editor for String Attributes

This editor is used to show, edit or create LDAP string attribute values.

Editor for string attributes

In the top area of this dialog, you see the distinguished name and type icon for the object whose attribute your are editing. In the line beneath, the attribute name is shown.

You can decide if you want to enter text in insert or override mode, just klick on the Overwrite label in the left bottom corner or press the Insert key to toggle this setting.


You can also decide if the text in the texbox should be line wrapped to fit into the text box or not - click on the Wrap label to change this setting:

String editing without word wrap

String editing with word wrap

When will the string editor will be used?


The string editor is used whenever LEX has valid schema information and detects one of the following official attribute syntaxes:

1.3.6.1.1.16.1

 UUID

1.3.6.1.4.1.1466.115.121.1.3

 Attribute Type Description

1.3.6.1.4.1.1466.115.121.1.6

 Bit String

1.3.6.1.4.1.1466.115.121.1.11

 Country String

1.3.6.1.4.1.1466.115.121.1.15

 Directory String

1.3.6.1.4.1.1466.115.121.1.16

 DIT Content Rule Description

1.3.6.1.4.1.1466.115.121.1.17

 DIT Structure Rule Description

1.3.6.1.4.1.1466.115.121.1.22

 Facsimile Telephone Number

1.3.6.1.4.1.1466.115.121.1.26

 IA5 String

1.3.6.1.4.1.1466.115.121.1.54

 LDAP Syntax Description

1.3.6.1.4.1.1466.115.121.1.56

 LDAP Schema Definition

1.3.6.1.4.1.1466.115.121.1.57

 LDAP Schema Description

1.3.6.1.4.1.1466.115.121.1.30

 Matching Rule Description

1.3.6.1.4.1.1466.115.121.1.31

 Matching Rule Use Description

1.3.6.1.4.1.1466.115.121.1.33

 MHS OR Address

1.3.6.1.4.1.1466.115.121.1.34

 Name And Optional UID

1.3.6.1.4.1.1466.115.121.1.35

 Name Form Description

1.3.6.1.4.1.1466.115.121.1.37

 Object Class Description

1.3.6.1.4.1.1466.115.121.1.39

 Other Mailbox

1.3.6.1.4.1.1466.115.121.1.41

 Postal Address

1.3.6.1.4.1.1466.115.121.1.43

 Presentation Address

1.3.6.1.4.1.1466.115.121.1.44

 Printable String

1.3.6.1.4.1.1466.115.121.1.58

 Substring Assertion

1.3.6.1.4.1.1466.115.121.1.45

 Subtree Specification

1.3.6.1.4.1.1466.115.121.1.50

 Telephone Number

1.3.6.1.4.1.1466.115.121.1.51

 Teletex Terminal Identifier

1.3.6.1.4.1.1466.115.121.1.52

 Telex Number

1.2.840.113556.1.4.905

 String(Teletext) {Microsoft}

1.2.840.113556.1.4.1362

 String(CaseSensitive) {Microsoft}

2.16.840.1.113719.1.1.5.1.6

 CaseIgnore List {Novell}

2.5.5.2

 String(Object-Identifier) {Microsoft}

2.5.5.3

 String(Case-Sensitive) {Microsoft}

2.5.5.4

 String(Teletext) {Microsoft}

2.5.5.5

 String(IA5/Printable) {Microsoft}

2.5.5.12

 String(Unicode) {Microsoft}

2.5.5.13

 Object(Presentation-Address) {MS}


On the other hand, if LEX assumes an attribute type as 'unknown' or if LEX could not evaluate the schema at all, it uses the string editor if the server returns the attribute value as a string and not as binary data. This would be the case for the following attribute syntaxes:

1.3.6.1.4.1.1466.115.121.1.1

 ACI Item

1.3.6.1.4.1.1466.115.121.1.2

 Access Point

1.3.6.1.4.1.1466.115.121.1.13

 Data Quality Syntax

1.3.6.1.4.1.1466.115.121.1.14

 Delivery Method

1.3.6.1.4.1.1466.115.121.1.18

 DL Submit Permission

1.3.6.1.4.1.1466.115.121.1.19

 DSA Quality Syntax

1.3.6.1.4.1.1466.115.121.1.20

 DSE Type

1.3.6.1.4.1.1466.115.121.1.21

 Enhanced Guide

1.3.6.1.4.1.1466.115.121.1.25

 Guide

1.3.6.1.4.1.1466.115.121.1.29

 Master And Shadow Access Points

1.3.6.1.4.1.1466.115.121.1.32

 Mail Preference

1.3.6.1.4.1.1466.115.121.1.55

 Modify Rights

1.3.6.1.4.1.1466.115.121.1.42

 Protocol Information

1.3.6.1.4.1.1466.115.121.1.46

 Supplier Information

1.3.6.1.4.1.1466.115.121.1.47

 Supplier Or Consumer

1.3.6.1.4.1.1466.115.121.1.48

 Supplier And Consumer

1.3.6.1.4.1.1466.115.121.1.49

 Supported Algorithm

2.16.840.1.113719.1.1.5.1.13

 Octet List {Novell}