Pre-defined Access Policies for Schema Registry
Based on a user’s responsibilities, you can add users or a user group to one or more of the following pre-defined access policies for Schema Registry and you can specify the type of permission such as Create, Read, Update, and Delete.
The following image shows the pre-defined access policies for Schema Registry:
The following table describes the pre-defined access policies for Schema Registry:
Access Policy | Description |
---|---|
all - export-import | Allows users to import and export schemas to/from the Schema
Registry service. For example, a user can import a .json file with schemas from a Confluent Kafka topic to Cloudera's Schema Registry. |
all - serde | Allows users to store metadata for the format of how data should be read and how it should be written. Users can store JAR files for serializers and deserializers and then map the serdes to the schema. |
all - schema-group, schema-metadata | Allows users to access the schema groups and schema metadata. |
all - schema-group, schema-metadata, schema-branch | Allows users to access the schema groups, schema metadata, and schema branch. |
all - registry-service | Allows users to access the schema registry service. If a user is added to this policy, the user can access all Schema Registry entities. |
all - schema-group, schema-metadata, schema-branch, schema-version | Allows users to access the schema groups, schema metadata, schema branch, and schema version. |