Setting access attributes for registry API views

On this page:

1. Overview

In addition to granting access to the registry for other registries or external systems in the Control Plane admin console (see Configuring registry access), the registry administrator must provide access to the views and REST API endpoints generated based on these views at the data model level.

You can configure access to the registry’s REST API views using access attributes at the Liquibase data model level. This way you can provide access to the registry API based on those views for other registries on the Platform or external systems.

Access to registry API views is configured using the <exposeSearchCondition> tag.

For details on the <exposeSearchCondition> tag, see Liquibase extensions for data modeling.

The <exposeSearchCondition> tag accepts several attributes: one for the search condition name, and others for various usage scenarios.

  • Providing access to the registry’s views and REST API for another registry on the Platform is done via the platform attribute.

  • Providing access to the registry’s views and REST API for an external system is done via the externalSystem attribute.

Example 1. XML schema example of using the tag and its attributes in the data model
<ext:exposeSearchCondition name="viewForDrop" platform="true" externalSystem="true" trembita="false"/>
  • name: Search condition name.

  • platform: Set to "true" to give access.

  • externalSystem: Set to "true" to give access.

To revoke access to the registry’s API views, set the corresponding attributes to false.

In this example, access to the registry data can be granted to another registry on the Platform, as well as to an external system.