Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Christopher Ng
OpenLDAP
Commits
96b403d9
Commit
96b403d9
authored
24 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
Flush out OID discussion
parent
73fa3bcc
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/guide/admin/slapdconfig.sdf
+20
-5
20 additions, 5 deletions
doc/guide/admin/slapdconfig.sdf
with
20 additions
and
5 deletions
doc/guide/admin/slapdconfig.sdf
+
20
−
5
View file @
96b403d9
...
...
@@ -797,15 +797,16 @@ clause is a shorthand for the clause "{{EX:dn=.* attr=member}}"
H2: Schema Specification
The {{EX:objectclass}} and {{attributeTypes}} configuration file
The {{EX:objectclass}} and {{
EX:
attributeTypes}} configuration file
directives can be used to define schema rules on entries in the
directory.
H3: Object Identifiers
Each schema element is identified by a globally unique Object
Identifier (OID). OIDs are also used to identify other objects.
They are commonly found in protocols described by ASN.1. In
Each schema element is identified by a globally unique
{{TERM[expand]OID}} ({{TERM:OID}}). OIDs are also used to identify
other objects.
They are commonly found in protocols described by {{TERM:ASN.1}}. In
particular, they are heavy used by Simple Network Management
Protocol (SNMP). As OIDs are hierarchical, your organization
can obtain one OID and branch in as needed. For example,
...
...
@@ -825,7 +826,14 @@ OID Assignment
!endblock
You are, of course, free to design a hierarchy suitable to your
organizational needs under your organization's OID.
organizational needs under your organization's OID. No matter
what hierarchy you choose, you should maintain a registry of
assignments you make. This can be a simple flat file or a
something more sophisticated such as the OpenLDAP OID Registry
{{URL:http://www.openldap.org/faq/index.cgi?file=197}}.
For more information about Object Identifers (and a listing
service) see {{URL:http://www.alvestrand.no/harald/objectid/}}.
.{{Under no circumstances should you use a fictious OID!}}
...
...
@@ -835,6 +843,13 @@ a OID under {{ORG[expand]IANA}} maintained
may request an OID to be assigned under this arch. Just fill
out the form at {{URL: http://www.iana.org/cgi-bin/enterprise.pl}}
and your official OID will be sent to you usually within a few days.
Your base OID will be something like {EX:1.3.6.1.4.1.X}} were {{EX:X}}
is an integer.
Note: Don't let the "MIB/SNMP" statement confuse you. OIDs
obtained using this form may be used for any purpose including
identifying LDAP schema elements.
H3: AttributeType Specification
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment