Core Schema
Core Schema define the core schema elements to load.
Core schema provider configuration.
Parent
The Core Schema object inherits from Schema Provider.
Core Schema Properties
You can use configuration expressions to set property values at startup time. For details, see Property Value Substitution.
Basic Properties
disabled-matching-rule
| Synopsis | The set of disabled matching rules. |
| Description | Matching rules must be specified using the syntax: OID, or use the default value 'NONE' to specify no value. |
| Default Value | NONE |
| Allowed Values | The OID of the disabled matching rule. |
| Multi-valued | Yes |
| Required | No |
| Admin Action Required | None |
| Advanced | No |
| Read-Only | No |
disabled-syntax
| Synopsis | The set of disabled syntaxes. |
| Description | Syntaxes must be specified using the syntax: OID, or use the default value 'NONE' to specify no value. |
| Default Value | NONE |
| Allowed Values | The OID of the disabled syntax, or NONE |
| Multi-valued | Yes |
| Required | No |
| Admin Action Required | None |
| Advanced | No |
| Read-Only | No |
enabled
| Synopsis | Indicates whether the Schema Provider is enabled for use. |
| Default Value | None |
| Allowed Values | true false |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced | No |
| Read-Only | No |
Advanced Properties
Use the --advanced option to access advanced properties.
allow-attribute-types-with-no-sup-or-syntax
| Synopsis | Indicates whether the schema should allow attribute type definitions that do not declare a superior attribute type or syntax |
| Description | When set to true, invalid attribute type definitions will use the default syntax. |
| Default Value | true |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
allow-zero-length-values-directory-string
| Synopsis | Indicates whether zero-length (that is, an empty string) values are allowed for directory string. |
| Description | This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it. |
| Default Value | false |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
java-class
| Synopsis | Specifies the fully-qualified name of the Java class that provides the Core Schema implementation. |
| Default Value | org.opends.server.schema.CoreSchemaProvider |
| Allowed Values | A Java class that extends or implements:
|
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
json-validation-policy
| Synopsis | Specifies the policy that will be used when validating JSON syntax values. |
| Default Value | strict |
| Allowed Values | disabled: JSON syntax values will not be validated and, as a result any sequence of bytes will be acceptable. lenient: JSON syntax values must comply with RFC 7159 except: 1) comments are allowed, 2) single quotes may be used instead of double quotes, and 3) unquoted control characters are allowed in strings. strict: JSON syntax values must strictly conform to RFC 7159. |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strict-format-boolean
| Synopsis | Indicates whether boolean values are required to strictly comply with the standard definition for this syntax. |
| Description | When set to true, only "TRUE" and "FALSE" will be acceptable, per RFC 4517. When set to false, the server will accept true/false, yes/no, 1/0, on/off. |
| Default Value | false |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strict-format-certificates
| Synopsis | Indicates whether X.509 Certificate values are required to strictly comply with the standard definition for this syntax. |
| Description | When set to false, certificates will not be validated and, as a result any sequence of bytes will be acceptable. |
| Default Value | true |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strict-format-country-string
| Synopsis | Indicates whether country code values are required to strictly comply with the standard definition for this syntax. |
| Description | When set to false, country codes will not be validated and, as a result any string containing 2 characters will be acceptable. |
| Default Value | true |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strict-format-jpeg-photos
| Synopsis | Indicates whether to require JPEG values to strictly comply with the standard definition for this syntax. |
| Default Value | false |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strict-format-telephone-numbers
| Synopsis | Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax. |
| Default Value | false |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |
strip-syntax-min-upper-bound-attribute-type-description
| Synopsis | Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off. |
| Description | When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly. |
| Default Value | false |
| Allowed Values | true false |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced | Yes |
| Read-Only | No |