dsconfig delete-schema-provider — Deletes Schema Providers
dsconfig delete-schema-provider
{options}
The dsconfig delete-schema-provider command takes the following options:
--provider-name {name}
The name of the Schema Provider.
Schema Provider properties depend on the Schema Provider type, which depends on the {name} you provide.
By default, OpenDJ directory server supports the following Schema Provider types:
Default {name}: Core Schema
Enabled by default: true
See the section called “Core Schema” for the properties of this Schema Provider type.
Default {name}: Json Schema
Enabled by default: true
See the section called “Json Schema” for the properties of this Schema Provider type.
-f | --force
Ignore non-existent Schema Providers.
Schema Provider properties depend on the Schema Provider type, which depends on the null you provide.
By default, OpenDJ directory server supports the following Schema Provider types:
Default null: Core Schema
Enabled by default: true
See the section called “Core Schema” for the properties of this Schema Provider type.
Default null: Json Schema
Enabled by default: true
See the section called “Json Schema” for the properties of this Schema Provider type.
Schema Providers of type core-schema have the following properties:
Indicates whether the schema should allow attribute type definitions that do not declare a superior attribute type or syntax When set to true, invalid attribute type definitions will use the default syntax.
true
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
Indicates whether zero-length (that is, an empty string) values are allowed for directory string. 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.
false
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
The set of disabled matching rules. Matching rules must be specified using the syntax: OID, or use the default value 'NONE' to specify no value.
NONE
The OID of the disabled matching rule.
Yes
No
None
No
No
The set of disabled syntaxes. Syntaxes must be specified using the syntax: OID, or use the default value 'NONE' to specify no value.
NONE
The OID of the disabled syntax, or NONE
Yes
No
None
No
No
Indicates whether the Schema Provider is enabled for use.
None
true
false
No
Yes
None
No
No
Specifies the fully-qualified name of the Java class that provides the Core Schema implementation.
org.opends.server.schema.CoreSchemaProvider
A Java class that implements or extends the class(es): org.opends.server.schema.SchemaProvider
No
Yes
None
Yes (Use --advanced in interactive mode.)
No
Specifies the policy that will be used when validating JSON syntax values.
strict
JSON syntax values will not be validated and, as a result any sequence of bytes will be acceptable.
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.
JSON syntax values must strictly conform to RFC 7159.
No
No
None
Yes (Use --advanced in interactive mode.)
No
Indicates whether X.509 Certificate values are required to strictly comply with the standard definition for this syntax. When set to false, certificates will not be validated and, as a result any sequence of bytes will be acceptable.
true
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
Indicates whether country code values are required to strictly comply with the standard definition for this syntax. When set to false, country codes will not be validated and, as a result any string containing 2 characters will be acceptable.
true
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
Indicates whether to require JPEG values to strictly comply with the standard definition for this syntax.
false
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
false
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
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. 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.
false
true
false
No
No
None
Yes (Use --advanced in interactive mode.)
No
Schema Providers of type json-schema have the following properties:
Indicates whether JSON string comparisons should be case-sensitive.
false
true
false
No
No
None
No
No
Indicates whether the Schema Provider is enabled for use.
None
true
false
No
Yes
None
No
No
Indicates whether JSON string comparisons should ignore white-space. When enabled all leading and trailing white space will be removed and intermediate white space will be reduced to a single character.
true
true
false
No
No
None
No
No
Specifies which JSON fields should be indexed. A field will be indexed if it matches any of the configured field patterns.
All JSON fields will be indexed.
A JSON pointer which may include wild-cards. A single '*' wild-card matches at most a single path element, whereas a double '**' matches zero or more path elements.
Yes
No
None
No
No
Specifies the fully-qualified name of the Java class that provides the Json Schema implementation.
org.opends.server.schema.JsonSchemaProvider
A Java class that implements or extends the class(es): org.opends.server.schema.SchemaProvider
No
Yes
None
Yes (Use --advanced in interactive mode.)
No
The name of the custom JSON matching rule.
The matching rule will not have a name.
A String
No
No
None
No
No
The numeric OID of the custom JSON matching rule.
None
The OID of the matching rule.
No
Yes
None
No
No