LDAP servers contain objectsorganized into hierarchies. Each object has an objectClasswhich specifies a number of attributes. Attributeshave values which describe an object. Figure 39illustrates a sample LDAP hierarchy which contains entries describing UA servers.
Figure 39– Sample LDAP Hierarchy
UA applications are stored in LDAP servers as entries with the UA defined objectClasses associated with them. The schema for the objectClasses defined for UA are shown in Table 117.
Table 117– LDAP Object Class Schema
|
Name |
LDAP Name |
Type |
OID |
|
Application |
opcuaApplication |
Structural |
1.2.840.113556.1.8000.2264.1.12.1 |
|
ApplicationName |
cn |
String (Required) |
Built-in |
|
HostName |
dNSName |
String |
Built-in |
|
ApplicationUri |
opcuaApplicationUri |
Name |
1.2.840.113556.1.8000.2264.1.12.1.1 |
|
ApplicationType |
opcuaApplicationType |
Boolean |
1.2.840.113556.1.8000.2264.1.12.1.3 |
|
DiscoveryUrl |
opcuaDiscoveryUrl |
String, Multi-valued |
1.2.840.113556.1.8000.2264.1.12.1.4 |
This OID is globally unique and can use used with any LDAP implementation.
Administrators may extend the LDAP schema by adding new attributes.