Data security: Data security is managed independently of web service. The same data security restrictions placed on a workspace or layer content are enforced for both OWS services and OGC API web services
Service security: OGC API web services are managed directly in Security > Services page. New access rules can be defined for OGC API services.
The collections resource can have a number of additional links, beyond
the basic ones that the service code already includes. Navigate to :menuselection:Settings>Global. The links are configured under heading OGC API Settings.
Link editor column description:
rel: the link relation type, as per the OGC API - Features specification
Mime type: the mime type for the resource found following the link
URL: the link URL
Title: the link title (optional)
Service: the service for which the link is valid (optional, defaults to all)
Common links relationships that could be added for the collections resource are:
enclosure, in case there is a package delivering all the collections (e.g. a GeoPackage, a ZIP full of shapefiles).
describedBy, in case there is a document describing all the collections (e.g. a JSON or XML schema).
license, if all collection data is under the same license.
Example from OGC API - Features service (http://localhost:8080/geoserver/ogc/features/v1/collections/?f=application%2Fjson):
Additional custom links can be provided for an individual layer. Use the Layer Editor :guilabel:Publishing tab, and locate the heading for OGC API.
The relationships are the same as for the collections resource, but used in case
there is anything that is specific to the collection (e.g., the schema for the single collection).
In addition, other relations can be specified, like the tag relation, to link to the eventual
INSPIRE feature concept dictionary entry.
Example from workspace ne:counteries collection providing enclosure for download: